https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
--- Comment #18 from Hans-Peter Nilsson ---
(In reply to Jiu Fu Guo from comment #17)
> > But "nobody" counts that close, so better say "no xtreme-header-* failures
> > since r13-5702-g72058eea9d407e".
>
> :) Since these failures occur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
--- Comment #17 from Jiu Fu Guo ---
> But "nobody" counts that close, so better say "no xtreme-header-* failures
> since r13-5702-g72058eea9d407e".
:) Since these failures occur erratically, so maybe reopen this or open a new
one if the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
--- Comment #16 from Hans-Peter Nilsson ---
(In reply to Hans-Peter Nilsson from comment #15)
> Fixed for cris-elf after r12-6062-gba64166bf81b6e but before-and-inclusive
> r12-6066-g6bcb6ed5a44b6f.
That was just counting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
Hans-Peter Nilsson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
--- Comment #14 from Jiu Fu Guo ---
Pass on trunk, gcc-12, gcc-11 for xtreme-header-* cases:
make check-gcc-c++ RUNTESTFLAGS="--target_board=unix'{-m64}'
modules.exp=xtreme-header-*"
=== g++ Summary ===
# of expected passes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853
Richard Biener changed:
What|Removed |Added
Target Milestone|12.3|12.4
--- Comment #13 from Richard
