> On 6 Jan 2018, at 04:53, Daniel Berlin via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>
>
>
> On Fri, Jan 5, 2018 at 8:39 PM, Andrew Kelley via llvm-dev <llvm-dev at
lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Greetings,
>
> I just found a bug in NewGVN: https://bugs.llvm.org/show_bug.cgi?id=35839
<https://bugs.llvm.org/show_bug.cgi?id=35839>
>
> I suspect this is a dupe of one of the three bugs we know about.
>
>
>
> I noticed that it's off by default in clang.
>
> Yup.
>
> I'm going to turn it off by default in zig too, since it has a bug.
>
> Every pass in LLVM has bugs :)
>
> What's the current status? Are we trying to move towards using it by
default in llvm 6.0.0? 7.0.0?
>
>
> I was the main contributor. I took on a new role and no longer have time to
push on it, and i don't suspect i will for at least 6-8 months, if not
longer.
> I suspect at some point it will become important enough for someone else to
push on it again.
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
Is there an umbrella PR or something that could help organise what someone would
have to do/take on in order for it to be enabled? Outstanding design issues or
critical blocking bugs etc.
Amara
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180108/6d18861e/attachment.html>