search for: uninititalized

...Ok-- I assume I should just add '-fno-stack-protector' to the llvm-gcc and clang command lines? I had totally missed that something like this was turned on by default. I'll re-run everything with this change, with frame pointers omitted, and dropping testcases that contain uses of uninititalized locals and post here again when that's done. Thanks for the feedback, John

On Dec 14, 2009, at 9:46 AMPST, Chris Lattner wrote: > > On Dec 14, 2009, at 7:33 AM, John Regehr wrote: > >> See here: >> >> http://embed.cs.utah.edu/embarrassing/ >> >> There is a lot of data there. Please excuse bugs and other problems. >> Feedback would be appreciated. > > Hi John, > > I agree with the gcc folks: it's really

On Dec 14, 2009, at 11:04 AM, Dale Johannesen wrote: >> >> I agree with the gcc folks: it's really important to get frame >> pointer >> emission etc aligned across the various compilers. ICC defaulting to >> frame pointers off and GCC/llvm defaulting to them on will seriously >> warp the numbers. > > Where did the gcc folks express this opinion?

...tack-protector' to the llvm- > gcc and > clang command lines? I had totally missed that something like this > was > turned on by default. Yes. > I'll re-run everything with this change, with frame pointers > omitted, and > dropping testcases that contain uses of uninititalized locals and post > here again when that's done. You'll probably need to some digging to make sure the defaults are exactly comparable. Are SSE and/or MMX used? This affects floating point codegen quite a bit. Are the target CPUs the same? I think some useful information is going...