public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95381] [11 Regression]: Bootstrap on m68k fails with ICE: in operator[], at vec.h:867
Date: Wed, 30 Dec 2020 17:38:27 +0000 [thread overview]
Message-ID: <bug-95381-4-DxB4tA7OL3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95381-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
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 <glaubitz at physik dot fu-berlin.de> ---
> (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 some printfs in warn_deprecated_use? But again, I'm a bit surprised
>> by the bisection results.
> I have verified it. I checked out eede1a6bf3a4f33fa5afef9e4dfc80c4dd89eeb3,
> reproduced the problem. Then reverted the change and it worked again.
>
> I honestly don't understand either how that commit could break the build.
>
>> http://3.14.90.209:8080/job/m68k-linux-gnu/
>>
>> Has the most recent build results from my tester. As you can see everything
>> built and regression tested on Dec 9. Dec 15 had a successful bootstrap,
>> but glibc failed due to a relatively minor bug in glibc.
> Is that a native bootstrap on qemu with "jit" enabled?
native bootstrap with qemu. Don't offhand remember if jit is enabled.
If not I can probably turn that on for the next one.
jeff
next prev parent reply other threads:[~2020-12-30 17:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 11:35 [Bug target/95381] New: " glaubitz at physik dot fu-berlin.de
2020-05-28 12:35 ` [Bug target/95381] " rguenth at gcc dot gnu.org
2020-05-28 13:03 ` glaubitz at physik dot fu-berlin.de
2020-05-28 21:34 ` glaubitz at physik dot fu-berlin.de
2020-06-09 17:00 ` law at redhat dot com
2020-06-12 10:38 ` glaubitz at physik dot fu-berlin.de
2020-06-16 22:44 ` law at redhat dot com
2020-10-16 11:48 ` rguenth at gcc dot gnu.org
2020-10-16 11:50 ` glaubitz at physik dot fu-berlin.de
2020-12-29 10:42 ` glaubitz at physik dot fu-berlin.de
2020-12-30 3:25 ` law at redhat dot com
2020-12-30 17:30 ` glaubitz at physik dot fu-berlin.de
2020-12-30 17:38 ` law at redhat dot com [this message]
2020-12-30 17:39 ` glaubitz at physik dot fu-berlin.de
2021-01-01 8:24 ` glaubitz at physik dot fu-berlin.de
2021-01-01 9:17 ` doko at debian dot org
2021-01-05 3:46 ` [Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k " law at redhat dot com
2021-01-14 8:55 ` rguenth at gcc dot gnu.org
2021-04-27 11:38 ` [Bug target/95381] [11/12 " jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2022-04-28 15:08 ` [Bug target/95381] [11/12/13 " glaubitz at physik dot fu-berlin.de
2022-04-28 16:04 ` [Bug target/95381] [11 " egallager at gcc dot gnu.org
2023-05-29 10:02 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-95381-4-DxB4tA7OL3@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).