On Thu, Mar 29, 2012 at 9:25 PM, John McCall <[email protected]> wrote:
> Author: rjmccall > Date: Thu Mar 29 23:25:14 2012 > New Revision: 153723 > > URL: http://llvm.org/viewvc/llvm-project?rev=153723&view=rev > Log: > When emitting a static local variable in C++, handle > the case that the variable already exists. Partly this is just > protection against people making crazy declarations with custom > asm labels or extern "C" names that intentionally collide with > the manglings of such variables, > We've started to see build failures due to this in libc-intercepting libraries. Is this expected? I'm still digging into the root cause, but I wanted to immediately point out that the diagnostic isn't very helpful here... foo/bar.cc:42:7: error: problem emitting static variable: already present > as different kind of symbol What kind of symbol was already present? Even better, can we (also) show the code that led to the symbol already being present in a note?
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
