search for: write_char

...gt;> not. > > Then just run the SCCP pass, and check to see if any operands satisfy > the predicate "isa<UndefValue>(V)". LLVM explicitly represents > undefined values. I have a case where it doesn't, but perhaps the SCCP pass isn't to blame: extern void write_char(int); const char foo[4] = "foo"; write_char(foo[0]); write_char(foo[5]); The write_char(foo[0]) correctly becomes write_char('f'), but the write_char(foo[5]) doesn't become undefined, instead staying as a GetElementPtrInst. I thought this might be because the optimize...

...hen just run the SCCP pass, and check to see if any operands satisfy >> the predicate "isa<UndefValue>(V)". LLVM explicitly represents >> undefined values. > > I have a case where it doesn't, but perhaps the SCCP pass isn't to blame: > > extern void write_char(int); > > const char foo[4] = "foo"; > > write_char(foo[0]); > write_char(foo[5]); > > The write_char(foo[0]) correctly becomes write_char('f'), but the > write_char(foo[5]) doesn't become undefined, instead staying as a > GetElementPtrInst. Well...

On Tue, 9 May 2006, Nick Lewycky wrote: >> You could do that, but SCCPSolver isn't really useful to mainline LLVM >> for anything other than SCCP and IPSCCP, so we don't need it in a public >> header. Out of curiosity, what are you looking to use the latice values >> for? Why not just run SCCP and then look at the transformed code? > > I was planning to

Chris Lattner wrote: > On Tue, 9 May 2006, Nick Lewycky wrote: > >>>> For an analysis pass, I'm interested in reading the lattice values >>>> calculated by SCCP. Should I split the current SCCP optimization >>>> into an >>>> analysis piece and the optimization that depends on it, so that I can >>>> use its analysis results?

...heck to see if any operands satisfy >>> the predicate "isa<UndefValue>(V)". LLVM explicitly represents >>> undefined values. >> >> >> I have a case where it doesn't, but perhaps the SCCP pass isn't to blame: >> >> extern void write_char(int); >> >> const char foo[4] = "foo"; >> >> write_char(foo[0]); >> write_char(foo[5]); >> >> The write_char(foo[0]) correctly becomes write_char('f'), but the >> write_char(foo[5]) doesn't become undefined, instead staying as...

...ewlib/libc/misc/__dprintf.c:223: attention : function declaration isn''t a prototype ../../../../../newlib-1.16.0/newlib/libc/misc/__dprintf.c:257: attention : function declaration isn''t a prototype ../../../../../newlib-1.16.0/newlib/libc/misc/__dprintf.c: In function ''write_char'': ../../../../../newlib-1.16.0/newlib/libc/misc/__dprintf.c:259: erreur: too many arguments to function ''_write_r'' ../../../../../newlib-1.16.0/newlib/libc/misc/__dprintf.c: Hors de toute fonction : ../../../../../newlib-1.16.0/newlib/libc/misc/__dprintf.c:268: attentio...