[cfe-dev] [LLVMdev] [PROPOSAL] per-function optimization level control
rnk at google.com
Wed May 29 07:54:21 PDT 2013
On Wed, May 29, 2013 at 10:17 AM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:
> On 29 May 2013 09:28, <Andrea_DiBiagio at sn.scee.net> wrote:
> > Hi,
> > I just wanted to bump this discussion in case anyone had any more
> > to make.
> > We're in a bit of a bind here as we've now had requests for this feature
> > from 10 separate customers, so we're going to be required to implement
> > this feature somehow in our private branch at least (all of the other
> > compilers they use already support some form of this feature so it is
> > heavily used in our field). Obviously we don't want to significantly
> > diverge from the mainline so it would be great to work with the community
> > to implement this in such a way that it could be incorporated into the
> > mainline and be beneficial to all of the other users too :-).
> What is the common use case? Making sure some funtion is always
> optimized or making sure it never optimized? If the second one, I
> wonder if marking it cold would be a good enough approximation.
> If we do need to enabled/disable passes run in each function, I would
> suggest starting by proposing which attributes should be added to the
> language reference.
Wasn't this already proposed?
LLVM already has optsize. Maybe it's just a matter of hooking up gcc's
attr(optimize) to it in clang, as a first approximation.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev