From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <rguenther@suse.de>
Cc: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
Jan Hubicka <hubicka@ucw.cz>, David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"William J. Schmidt" <wschmidt@linux.vnet.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: move increase_alignment from simple to regular ipa pass
Date: Wed, 08 Jun 2016 15:09:00 -0000 [thread overview]
Message-ID: <20160608150855.GB2550@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1606081610370.1493@t29.fhfr.qr>
> I think it would be nice to work towards transitioning
> flag_section_anchors to a flag on varpool nodes, thereby removing
> the Optimization flag from common.opt:fsection-anchors
>
> That would simplify the walk over varpool candidates.
Makes sense to me, too. There are more candidates for sutff that should be
variable specific in common.opt (such as variable alignment, -fdata-sctions,
-fmerge-constants) and targets. We may try to do it in an easy to extend way
so incrementally we can get rid of those global flags, too.
One thing that needs to be done for LTO is sane merging, I guess in this case
it is clear that the variable should be anchored when its previaling definition
is.
Honza
>
> Richard.
>
> > Thanks,
> > Prathamesh
> > >
> > > Honza
> > >>
> > >> Richard.
> >
> >
>
> --
> Richard Biener <rguenther@suse.de>
> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
next prev parent reply other threads:[~2016-06-08 15:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 12:52 David Edelsohn
2016-06-02 12:57 ` Richard Biener
2016-06-02 15:01 ` Jan Hubicka
2016-06-03 7:57 ` Richard Biener
2016-06-03 8:05 ` Jan Hubicka
2016-06-07 8:34 ` Prathamesh Kulkarni
2016-06-08 14:15 ` Richard Biener
2016-06-08 15:09 ` Jan Hubicka [this message]
2016-06-09 20:18 ` Prathamesh Kulkarni
2016-06-09 20:23 ` Jan Hubicka
2016-06-10 9:33 ` Prathamesh Kulkarni
2016-06-10 11:17 ` Richard Biener
2016-06-13 8:57 ` Prathamesh Kulkarni
2016-06-13 10:43 ` Jan Hubicka
2016-06-14 13:02 ` Prathamesh Kulkarni
2016-06-17 14:22 ` Prathamesh Kulkarni
2016-06-23 17:21 ` Prathamesh Kulkarni
2016-06-28 9:27 ` Prathamesh Kulkarni
2016-07-05 9:53 ` Prathamesh Kulkarni
2016-07-20 11:49 ` Prathamesh Kulkarni
-- strict thread matches above, loose matches on Subject: below --
2016-06-01 10:17 Prathamesh Kulkarni
2016-06-01 13:07 ` Richard Biener
2016-06-02 7:29 ` Prathamesh Kulkarni
2016-06-02 7:53 ` Richard Biener
2016-06-02 9:15 ` Prathamesh Kulkarni
2016-06-02 9:24 ` Prathamesh Kulkarni
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=20160608150855.GB2550@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=prathamesh.kulkarni@linaro.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.com \
/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).