This is the mail archive of the gcc-patches@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]

Re: Fix PR 53743 and other -freorder-blocks-and-partition failures (issue6823047)


> On Sat, May 11, 2013 at 1:19 PM, Jan Hubicka wrote:
> > Once -freorder-blocks-and-partition actually works, we should enable it by
> > default with -fprofile-generate (I recall I was trying to do that once, but
> > I am not sure what was outcome back then and why it did not happen).
> > That should get it tested with profiledbootstrap, too.
> 
> I don't think -freorder-blocks-and-partition ever was stable enough to
> work with profiledbootstrap. From day one, it was fragile and not well
> covered in regression testing. I hope the verifiers will make life a
> bit more bearable, and that the fixes from Teresa will allow us to
> enable -freorder-blocks-and-partition with -fprofile-generate.

Yep, I hoped to slowly chase the bugs away but always got scared by
implementation details....
> 
> Has anyone ever investigated the effects of
> -freorder-blocks-and-partition vs. the function splitting part if
> flag_partial_inlining (ipa-split.c)?

ipa-split really does splitting just in very special cases where partial
inlining seems possible and feasible. Plus one really split function into
two making it impossible to mix local vars. So it is not a replacement for
partitioning...

I was considering more aggressive outlininning of cold parts in ipa-split,
but did not get it implemented yet.

Honza
> 
> Ciao!
> Steven


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