public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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: Tue, 02 Jan 2024 15:04:49 +0000	[thread overview]
Message-ID: <bug-113140-4-5kC4hT2HQm@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 #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Rainer Orth <ro at gcc dot gnu.org> ---

> It's also helpful to include the cc1plus invocation from g++ -v; that includes
> all you need to reproduce.

The full one is

cc1plus -fpreprocessed qv4qobjectwrapper.cpp.ii -mptr64 -mstack-bias
-mno-v8plus -quiet -m64 -mcpu=v9 -g -O2 -std=c++17 -version -flto=auto
-ffat-lto-objects -fstack-protector-strong -fPIC -fvisibility=hidden
-fvisibility-inlines-hidden -fno-exceptions -o qv4qobjectwrapper.cpp.s

With the original testcase and cc1plus from the gcc-13 branch, this can
be reduced to

cc1plus -fpreprocessed qv4qobjectwrapper.cpp.ii -mptr64 -mstack-bias
-mno-v8plus -quiet -m64 -mcpu=v9 -O2 -fno-exceptions -o qv4qobjectwrapper.cpp.s

while without -fno-exceptions the test compiles in this configuration.

Fortunately, I managed to reduce the testcase as attached, which SEGVs
even without -fno-exceptions.

On trunk, the original testcase compiles without issues, while the
reduced one SEGVs since gcc-8 (didn't try before) up to trunk.

  parent reply	other threads:[~2024-01-02 15: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 ` [Bug target/113140] " sjames at gcc dot gnu.org
2023-12-25 22:08 ` 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 [this message]
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-5kC4hT2HQm@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).