[llvm-bugs] [Bug 46331] New: Merge 0cecafd647cc into 10.0.1
via llvm-bugs
llvm-bugs at lists.llvm.org
Mon Jun 15 10:40:42 PDT 2020
https://bugs.llvm.org/show_bug.cgi?id=46331
Bug ID: 46331
Summary: Merge 0cecafd647cc into 10.0.1
Product: new-bugs
Version: 10.0
Hardware: PC
OS: All
Status: NEW
Severity: release blocker
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: dimitry at andric.com
CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org
Please merge https://reviews.llvm.org/rG0cecafd647cc into 10.0.1. As described
in https://bugs.freebsd.org/246630, clang's new -fintegrated-cc1 default
(introduced in https://reviews.llvm.org/rGc4a134a5107c and some follow-up
commits) appears to have uncovered non-determinism in the assembly output. This
is further described in https://reviews.llvm.org/D69825, the original review
for
https://reviews.llvm.org/rGc4a134a5107c.
In FreeBSD I have worked around the problem temporarily, by setting
CLANG_SPAWN_CC1 back to 1, so a fresh clang -cc1 process is executed.
But after some more testing and bisecting, I found out that the non-determinism
is actually fixed by https://reviews.llvm.org/rG0cecafd647cc ("[BasicAA] Make
BasicAA a cfg pass"). In https://reviews.llvm.org/D69825#2091632 I've asked
@asbirlea if this was an intended side-effect of the commit, or if there is
something different going on.
In any case, this bug should be solved one way or another in 10.0.1, as
non-determinism is obviously a blocker.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200615/3a74355e/attachment.html>
More information about the llvm-bugs
mailing list