echristo at apple.com
Wed Feb 17 10:01:25 PST 2010
On Feb 17, 2010, at 9:44 AM, David Greene wrote:
> On Monday 15 February 2010 20:46:52 Daniel Dunbar wrote:
>>> BTW, how sure are we that all these are gcc issues and not some incorrect
>>> code somewhere that triggers undefined behavior?
>> Medium sure? :)
>> I spent a little while hunting this particular bug, and it acted very
>> much like a compiler bug. I never narrowed it down to a test case,
> Is there a gcc bug for this testcase? I'd like to understand better exactly
> what the issue is.
> Looking at http://llvm.org/docs/GettingStarted.html#brokengcc here's the
> current recommendation:
> We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1 successfully with them
> (however, see important notes below).
> Is this really still true? Is there a later version of gcc that's
> recommended? 3.4.x is ancient. Does the page need an update?
> What are people out there using today?
SnowLeopard had a 4.2 derivative as well and seems to be working fine.
More information about the llvm-dev