From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <rguenther@suse.de>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org
Subject: Re: -fstrict-aliasing fixes 6/6: permit inlining of comdats
Date: Mon, 07 Dec 2015 18:52:00 -0000 [thread overview]
Message-ID: <20151207185231.GA10655@kam.mff.cuni.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1512070916290.4884@t29.fhfr.qr>
> >
> > Well, not exactly of the case mentioned above, but still think that this is
> > safe (ugly, too). An alternative is to keep around the bodies until after
> > inlining. I have infrastructure for that in my tree, but it is hard to tune to
> > do: first the alternative function body may have different symbol references
> > (as a result of different early inlinin) which may not be resolved in current
> > binary so we can not use it at all. Second keepin many alternatives of every
> > body around makes code size estimates in inliner go crazy.
>
> /me inserts his usual "partitioning to the rescue" comment...
>
> ;)
Hmm, OK. I fail to see how that would save the day here :) It is not a problem about
the fact that we can not switch flags according the function but about the linking
that happens prior partitioning.
Honza
>
> Richard.
prev parent reply other threads:[~2015-12-07 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 7:37 Jan Hubicka
2015-12-04 11:20 ` Richard Biener
2015-12-04 16:57 ` Jan Hubicka
2015-12-04 18:04 ` Jan Hubicka
2015-12-04 18:08 ` Jan Hubicka
2015-12-07 8:20 ` Richard Biener
2015-12-07 18:53 ` Jan Hubicka
2015-12-04 23:39 ` H.J. Lu
2015-12-07 8:16 ` Richard Biener
2015-12-07 18:52 ` Jan Hubicka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151207185231.GA10655@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).