https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
Matthias Klose changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #15
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #14 from John Paul Adrian Glaubitz ---
Quick update. The bug actually occurs with "--disable-bootstrap" which is how
Matthias Klose configures gcc when building the gcc-snapshot package. Removing
the configure flag makes the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #13 from John Paul Adrian Glaubitz ---
(In reply to Jeffrey A. Law from comment #12)
> On 12/30/20 10:30 AM, glaubitz at physik dot fu-berlin.de wrote:
> > Is that a native bootstrap on qemu with "jit" enabled?
>
> native bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #12 from Jeffrey A. Law ---
On 12/30/20 10:30 AM, glaubitz at physik dot fu-berlin.de wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
>
> --- Comment #11 from John Paul Adrian Glaubitz fu-berlin.de> ---
> (In reply to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #11 from John Paul Adrian Glaubitz ---
(In reply to Jeffrey A. Law from comment #10)
> So if that bisection is accurate, the only way this could be failing would
> be if something with a deprecated attribute is being used.
>
> Maybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #10 from Jeffrey A. Law ---
So if that bisection is accurate, the only way this could be failing would be
if something with a deprecated attribute is being used.
Maybe some printfs in warn_deprecated_use? But again, I'm a bit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #9 from John Paul Adrian Glaubitz ---
I have bisected this now and it turns out, the regression was introduced by:
commit eede1a6bf3a4f33fa5afef9e4dfc80c4dd89eeb3
Author: Nick Clifton
Date: Mon Jun 18 10:39:01 2018 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #8 from John Paul Adrian Glaubitz ---
(In reply to Richard Biener from comment #7)
> Still broken?
Unfortunately, yes:
> https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot=m68k=1%3A20201002-1=1601807222=0
echo timestamp >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #7 from Richard Biener ---
Still broken?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #6 from Jeffrey A. Law ---
That's an indication that something has tried to do an out of bounds read on a
VEC object. The call chain points back to the initial quick_grow of an
auto_vec from test_vector_cst_patterns -- which is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #5 from John Paul Adrian Glaubitz ---
Here's what I get on qemu-m68k-system (instead of qemu-user):
root@pacman:/srv/gcc-debug/build-jit/gcc# ./xgcc -B ./ -xc++ -nostdinc
/dev/null -S -o /dev/null
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #3 from John Paul Adrian Glaubitz ---
(In reply to John Paul Adrian Glaubitz from comment #2)
> (In reply to Richard Biener from comment #1)
> > can we have a backtrace?
>
> Working on it.
I'm at the point now where I can invoke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #2 from John Paul Adrian Glaubitz ---
(In reply to Richard Biener from comment #1)
> can we have a backtrace?
Working on it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
15 matches
Mail list logo
