[LLVMbugs] [Bug 15341] New: Codegen creates two distinct types for same Clang type
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Sat Feb 23 14:01:41 PST 2013
http://llvm.org/bugs/show_bug.cgi?id=15341
Bug ID: 15341
Summary: Codegen creates two distinct types for same Clang type
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangbugs at nondot.org
Reporter: wolfeinstein at gmail.com
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
When using CodeGenModule class to code generate a module, GetAddrOfGlobal is
used to ensure that a global variable is actually saved and created in the
module. Then the module is released and linked into a second module.
Given
VarDecl* vd = ...
which is a global variable, then
codegen.getTypes().ConvertType(vd->getType());
is not the same LLVM type as
module.getGlobalVariable(codegen.MangleName(vd));
after indirection has been accounted for. Clang creates identical named and
unnamed LLVM type. This is after CodeGenModule::Release() has been called. The
test I have been working with is simply std::cout in <iostream>. This causes
spurious LLVM type errors. I am using Windows 7 x64, VS 2012, targetting MinGW
and using libstdc++ 4.6.3, and Clang is r175973.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20130223/03225964/attachment.html>
More information about the llvm-bugs
mailing list