Do we really need a CPP manual?

2016-12-15 Thread Sandra Loosemore
I've had an item on my todo list for a while to try to update the CPP manual, mainly because I've been aware that it has duplicate entries for several of the same command-line options that appear in invoke.texi that have gotten bit-rotten or otherwise out of sync with respect to the GCC manual

gcc-6-20161215 is now available

2016-12-15 Thread gccadmin
Snapshot gcc-6-20161215 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20161215/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Jakub Jelinek
On Thu, Dec 15, 2016 at 10:10:31PM +0100, Jan Hubicka wrote: > > So here is a proof of concept of an attribute that disables inlining, > > cloning, ICF, IPA VRP, IPA bit CCP, IPA RA, pure/const/throw discovery. > > Does it look reasonable? Anything still missing? > > I think you also want to disa

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Florian Weimer
* Alexander Monakov: > 2. Can we gently suggest to readers of documentation that this was > invented for use in the GCC testsuite, and encourage them to seek > proper alternatives, e.g.: > > This attribute is exposed for the purpose of testing the compiler. > In general it should be preferable

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Jan Hubicka
> Hi! > > So here is a proof of concept of an attribute that disables inlining, > cloning, ICF, IPA VRP, IPA bit CCP, IPA RA, pure/const/throw discovery. > Does it look reasonable? Anything still missing? I think you also want to disable optimizations we do about local functions (stack alignment

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Florian Weimer
* Jakub Jelinek: > On Thu, Dec 15, 2016 at 07:11:09PM +0100, Florian Weimer wrote: >> * Jakub Jelinek: >> >> > + if (lookup_attribute ("used", attributes) == NULL) >> > + attributes = tree_cons (get_identifier ("used"), NULL, attributes); >> >> Attribute “used” seems different to me from

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Jakub Jelinek
On Thu, Dec 15, 2016 at 07:11:09PM +0100, Florian Weimer wrote: > * Jakub Jelinek: > > > + if (lookup_attribute ("used", attributes) == NULL) > > + attributes = tree_cons (get_identifier ("used"), NULL, attributes); > > Attribute “used” seems different to me from the rest. Based on the >

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Florian Weimer
* Jakub Jelinek: > + if (lookup_attribute ("used", attributes) == NULL) > + attributes = tree_cons (get_identifier ("used"), NULL, attributes); Attribute “used” seems different to me from the rest. Based on the documentation, I wouldn't expect it to have any action-at-a-distance effect

Re: [RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Alexander Monakov
On Thu, 15 Dec 2016, Jakub Jelinek wrote: > So here is a proof of concept of an attribute that disables inlining, > cloning, ICF, IPA VRP, IPA bit CCP, IPA RA, pure/const/throw discovery. > Does it look reasonable? Anything still missing? I'd like to suggest some additions to the extend.texi entr

[RFC] noipa attribute (was Re: How to avoid constant propagation into functions?)

2016-12-15 Thread Jakub Jelinek
Hi! So here is a proof of concept of an attribute that disables inlining, cloning, ICF, IPA VRP, IPA bit CCP, IPA RA, pure/const/throw discovery. Does it look reasonable? Anything still missing? No testsuite coverage yet, I bet we'd want to check for all those opts and see that they aren't happen