This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/56593] LTO profiledbootstrap fails for Ada
- From: "steven at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 12 Mar 2013 17:19:56 +0000
- Subject: [Bug bootstrap/56593] LTO profiledbootstrap fails for Ada
- Auto-submitted: auto-generated
- References: <bug-56593-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56593
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #5 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-12 17:19:56 UTC ---
(In reply to comment #4)
> > Is there any advantage in putting nested functions in different
> > partition from the parent function? I'd say LTO just should try
> > hard to make to put them into the same partition.
>
> That would be an arbitrary restriction though. This works fine,
> except that -g currently breaks, but (1) it doesn't really work
> with LTO in any case and (2) nested functions don't really work
> with -g at high optimization level either.
What "it" do you mean at (1)?
Putting nested functions in the same partition as the parent is not
really arbitrary. Nested functions have a limited scope, and AFAIU
are only accessible from the parent function. There can't be much
for IPA to do with nested functions in another partition.