[cfe-dev] [LLVMdev] LLVM 3.4 Branch Freeze

James Courtier-Dutton james.dutton at gmail.com
Fri Dec 13 09:35:28 PST 2013

On 13 December 2013 05:24, Hal Finkel <hfinkel at anl.gov> wrote:
> Bill, et al.,
> There are still a number of open bug reports demonstrating miscompiles on x86 with small/reduced test cases. I propose that we either delay this release until these have been fixed, or plan on a point release in the near future. I recommend that we put out another two release candidates, one at the end of this week, and one after another two weeks or so, to allow for these outstanding issues to be resolved.
> Specifically, I think that these issues should be resolved prior to the release of 3.4:
>  PR18068 [BasicAA]
>  PR18067 [GVN]
>  PR16431 (multiple; I suspect covered by the previous two)
>  PR17638 [IndVarSimplify]
>  PR18223 [IndVarSimplify]
>  PR17473 [LSR]
>  PR18165 [LSR]
>  PR16729 [Loop Vectorizer]
>  PR17288 [Loop Vectorizer]
>  PR18102 [x86 backend or CodeGen]
>  PR18000 [x86 backend or CodeGen]
>  PR17504 [x86 backend or CodeGen]
>  PR17794
>  PR17073
>  PR16108
>  PR18042 [LCSSA] (This hits an assert, but may miscompile with NDEBUG)
> Of course, the same underlying bug may be causing more than one of these, and at least some of these are already being worked on. Thoughts?
> Thanks again,
> Hal

Even if they take a long time to fix. What is the harm in adding a
test case for each one into the release 3.4 now?
It sounds to me that they are unlikely to be marked as "won't fix".
They will then come up as tests that fail and can be listed as "Known
bugs" in the release notes. Although there does not appear to be a
"Known bugs" list in the release notes at present.
Someone might even be able to use them to make an "automated compare"
that can compare them with various large projects and be able to
obtain an answer as to whether the project will compile correctly or
not with clang/llvm.


More information about the cfe-dev mailing list