Without seeing more details it's impossible to tell, but it might have been
me.
https://github.com/llvm/llvm-project/commit/6102310d814ad73eab60a88b21dd70874f7a056f#diff-0f9a49c4e31c311a0010e126cd785f08
changed PHI node equality check, but there were some users that
implicitly depended
on the old definition of the PHI equality, and didn't verify their
implicit assumptions with reality,
which eventually manifested as stage2-stage3 clang mismatches.
This was finally fixed in
https://github.com/llvm/llvm-project/commit/5ec2b757cc7d37ff0d03b36ee863b0962fe78108
and they have been taught to check with reality in
https://github.com/llvm/llvm-project/commit/961483a5ea7c0e628c025187287d1658457ffcb3
so this should be caught earlier next time.
Roman
On Sun, Aug 30, 2020 at 5:53 AM Johannes Doerfert via llvm-dev
<llvm-dev at lists.llvm.org> wrote:>
> Hi Itaru,
>
> (this time with the list CC'ed)
>
> I am not sure what failure you see but our buildbots look mostly green:
> http://lab.llvm.org:8011/waterfall
>
> Please provide more details as it is hard to determine if this is an
> LLVM issue or not.
>
> Thanks,
> Johannes
>
>
> On 8/29/20 6:40 PM, Itaru Kitayama via llvm-dev wrote:
> > I am seeing in the last couples of days llvm plus other projects
builds are
> > failing, is this being worked on?
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev