On 5/5/22 18:21, H.J. Lu wrote: > On Thu, May 5, 2022 at 4:24 AM Martin Liška <mli...@suse.cz> wrote: >> >> On 5/5/22 01:07, H.J. Lu wrote: >>> On Wed, May 4, 2022 at 1:59 AM Martin Liška <mli...@suse.cz> wrote: >>>> >>>> Hello. >>>> >>>> I'm going to do merge from upstream. >>>> >>>> Patch can bootstrap on x86_64-linux-gnu and survives regression >>>> tests. I've also tested on ppc64le-linux-gnu and verified the ABI. >>>> >>>> The only real change is a small change in >>>> gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c where we >>>> need --param=asan-use-after-return=0. >>>> >>>> I'm going to push the patches. >>> >>> Hi, >>> >>> I am checking in this patch to cherry-pick >>> >>> f52e365092aa [sanitizer] Use newfstatat for x32 >>> >>> to restore x32 build. >>> >> >> I'm going to do one more merge from upstream >> (75f9e83ace52773af65dcebca543005ec8a2705d) as we want to include Tobias's >> revision 6f095babc2b7d564168c7afc5bf6afb2188fd6b4 and my >> revision f1b9245199f3457a4d06d32d1bc6e44573c166e3. > > I am testing a patch for > > https://github.com/llvm/llvm-project/issues/55288 > > to fix: > > https://gcc.gnu.org/pipermail/gcc-regression/2022-May/076571.html
Interesting. How did you run these tests that the error shows up? > > The same bug is also in GCC 12. But somehow, it doesn't show up in > GCC tests. So please backport it once it's merged. Martin
