search for: unsimplified

On Feb 20, 2013 7:58 AM, "Krzysztof Parzyszek" <kparzysz at codeaurora.org> wrote: > > On 2/19/2013 11:11 PM, Chris Lattner wrote: >> >> >> I still really have no idea what problem you think you are solving. > > > Dealing with different attributes on different functions. > > --- a.c --- > void func_a() { > printf(...); > } > >

On 2/19/2013 11:11 PM, Chris Lattner wrote: > > I still really have no idea what problem you think you are solving. Dealing with different attributes on different functions. --- a.c --- void func_a() { printf(...); } --- b.c --- void func_b() { printf(...); func_a(); } a.c is compiled with no-builtin-printf, b.c has no such options. The prototype approach (no-builtin on the

On 2/20/2013 10:19 AM, David Blaikie wrote: > > I'm still not understanding a few things in this thread, including one > here: if you annotate only the calls to print (say) then how do you > handle the indirect calls that the back end might yet optimize down to a > constant & then attempt to simplify? Would all indirect calls be > annotated with all the unsimplifiable

On Wed, Jan 22, 2014 at 1:01 AM, Andrew Trick <atrick at apple.com> wrote: > On Jan 22, 2014, at 12:44 AM, Chandler Carruth <chandlerc at gmail.com> > wrote: > > > On Wed, Jan 22, 2014 at 12:33 AM, Andrew Trick <atrick at apple.com> wrote: > >> > There appear to be two chunks of "functionality" provided by loop >> passes: >> >

Responding to both David and Krzysztof, I'm sorry if this thread has gotten way-over-confusing. I really don't think it's this complicated: :) On Feb 20, 2013, at 8:19 AM, David Blaikie <dblaikie at gmail.com> wrote: > > Dealing with different attributes on different functions. > > > > --- a.c --- > > void func_a() { > > printf(...); > > }

On Feb 20, 2013 8:32 AM, "Krzysztof Parzyszek" <kparzysz at codeaurora.org> wrote: > > On 2/20/2013 10:19 AM, David Blaikie wrote: >> >> >> I'm still not understanding a few things in this thread, including one >> here: if you annotate only the calls to print (say) then how do you >> handle the indirect calls that the back end might yet