On Mon, Mar 26, 2012 at 8:51 PM, Steven Bosscher <stevenb....@gmail.com> wrote:
> On Mon, Mar 26, 2012 at 8:22 PM, H.J. Lu <hjl.to...@gmail.com> wrote:
>> It may have caused:
> It certainly seems so. Looking into it...
Java is the culprit. I'm going to commit the following patch to paper
over the issue for now.
--- varasm.c (revision 185823)
+++ varasm.c (working copy)
@@ -2170,6 +2170,10 @@
If it's not, we should not be calling this function. */
+ /* In a perfect world, the following condition would be true.
+ Sadly, the Java and Go front ends emit assembly *from the front end*,
+ bypassing the call graph. See PR52739. Fix before GCC 4.8. */
/* This function should only be called if we are expanding, or have
expanded, to RTL.
Ideally, only final.c would be calling this function, but it is
@@ -2177,6 +2181,7 @@
for further discussion. */
gcc_assert (cgraph_state == CGRAPH_STATE_EXPANSION
|| cgraph_state == CGRAPH_STATE_FINISHED);
if (!DECL_P (decl) || !DECL_EXTERNAL (decl) || !TREE_PUBLIC (decl))