This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug middle-end/48585] [4.7 Regression] 483.xalancbmk in SPEC CPU 2006 failed to build


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48585

--- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> 2011-04-20 18:17:14 UTC ---
Actually, IPA-CP is clearly involved, the function we're inlinig to
is:

(gdb) call debug_generic_expr(id->dst_fn)
_ZN10xalanc_1_818XalanDOMStringPoolC2Emmm.constprop.15285

Looking at the WPA cgraph dump, it is apparent that also the src_fn is
cloned by IPA-CP.  However, it remains to be seen why the original and
not the clone is being inlined here.  When I look at the ASM name of
the src function:

(gdb) call debug_generic_expr(decl_assembler_name(id->src_fn))
_ZN10xalanc_1_818XalanDOMStringPoolC2Emmm.9230

And then it up in WPA cgraph_node, it shows no callers or callees at
all:

__base_ctor /77004(-1) @0x7f91ca86f000 (asm:
_ZN10xalanc_1_818XalanDOMStringPoolC2Emmm) availability:n
ot_available local prevailing_def_ironly finalized
  called by:
  calls:
  References:
  Refering this function:
  aliases & thunks: __comp_ctor /77005 (asm:
_ZN10xalanc_1_818XalanDOMStringPoolC1Emmm)

So I don't quite understand how it can be scheduled to be inlined...


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]