public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "charlet at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98341] [11 Regression] Ada bootstrap fails with Storage_Error stack overflow or erroneous memory access on m68k Date: Sun, 07 Feb 2021 12:01:12 +0000 [thread overview] Message-ID: <bug-98341-4-EmvzCNbSaB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98341-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98341 --- Comment #9 from Arnaud Charlet <charlet at gcc dot gnu.org> --- The problem is somehow specific to m68k, for some unknown reason. There is nothing target specific in the change, no assumption is made on the underlying target. What we need now is a debugging session from someone who has a setup to reproduce.
next prev parent reply other threads:[~2021-02-07 12:01 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 8:31 [Bug target/98341] New: " glaubitz at physik dot fu-berlin.de 2020-12-18 8:00 ` [Bug target/98341] " mikpelinux at gmail dot com 2020-12-22 8:44 ` glaubitz at physik dot fu-berlin.de 2020-12-22 15:29 ` mhillen at linux dot ibm.com 2020-12-26 20:19 ` glaubitz at physik dot fu-berlin.de 2021-01-14 8:10 ` rguenth at gcc dot gnu.org 2021-02-04 10:50 ` mikpelinux at gmail dot com 2021-02-04 10:58 ` glaubitz at physik dot fu-berlin.de 2021-02-04 11:05 ` charlet at gcc dot gnu.org 2021-02-07 11:30 ` glaubitz at physik dot fu-berlin.de 2021-02-07 12:01 ` charlet at gcc dot gnu.org [this message] 2021-02-07 12:03 ` glaubitz at physik dot fu-berlin.de 2021-04-09 8:00 ` rguenth at gcc dot gnu.org 2021-04-27 11:39 ` [Bug target/98341] [11/12 " jakub at gcc dot gnu.org 2021-05-02 9:02 ` reiter.christoph at gmail dot com 2021-05-02 9:32 ` ebotcazou at gcc dot gnu.org 2021-05-02 9:33 ` [Bug target/98341] [11/12 Regression] Ada bootstrap fails with " ebotcazou at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-02-23 10:06 ` glaubitz at physik dot fu-berlin.de 2022-02-23 10:18 ` ebotcazou at gcc dot gnu.org 2022-02-23 10:33 ` glaubitz at physik dot fu-berlin.de 2022-02-24 9:57 ` glaubitz at physik dot fu-berlin.de 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2022-04-28 15:02 ` [Bug target/98341] [11/12/13 " glaubitz at physik dot fu-berlin.de 2022-04-28 16:02 ` [Bug target/98341] [11 " egallager at gcc dot gnu.org 2023-05-29 10:03 ` 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-98341-4-EmvzCNbSaB@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: linkBe 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).