public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113140] [SPARC] [13 Regression] Segmentation fault during RTL pass: dbr Date: Mon, 25 Dec 2023 20:04:42 +0000 [thread overview] Message-ID: <bug-113140-4-KTUkXjGtOm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113140 --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- Could you try ro tun that failing command again with -save-temps appended, and then upload qv4qobjectwrapper.ii? It should be somewhere in the builddir.
next prev parent reply other threads:[~2023-12-25 20:04 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-25 19:52 [Bug target/113140] New: " glaubitz at physik dot fu-berlin.de 2023-12-25 20:04 ` sjames at gcc dot gnu.org [this message] 2023-12-25 22:08 ` [Bug target/113140] " glaubitz at physik dot fu-berlin.de 2023-12-26 5:18 ` pinskia at gcc dot gnu.org 2024-01-02 14:54 ` ro at gcc dot gnu.org 2024-01-02 14:55 ` ro at gcc dot gnu.org 2024-01-02 15:04 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-02 15:06 ` ro at gcc dot gnu.org 2024-01-06 10:08 ` ebotcazou at gcc dot gnu.org 2024-01-08 14:02 ` [Bug target/113140] [13/14 regression] segmentation fault during delay slot scheduling rguenth at gcc dot gnu.org 2024-01-09 8:54 ` [Bug rtl-optimization/113140] " ebotcazou at gcc dot gnu.org 2024-01-09 9:25 ` cvs-commit at gcc dot gnu.org 2024-01-09 9:26 ` cvs-commit at gcc dot gnu.org 2024-01-09 9:27 ` ebotcazou 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-113140-4-KTUkXjGtOm@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).