public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93808] [9/10/11/12 Regression] [SH] Ruby crashes with 'Illegal Instruction' with -fcrossjumping
Date: Sun, 02 May 2021 09:22:17 +0000	[thread overview]
Message-ID: <bug-93808-4-ix5u1kPrA4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93808-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93808

--- Comment #31 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to John Paul Adrian Glaubitz from comment #30)
> Created attachment 50717 [details]
> Build log for ruby 2.5 with Oleg's patch applied

Ah, I forgot to add -O1 and -fno-cross-jumping to CFLAGS.

Are the builtin_traps() optimized out for -O2?

I'm building with the correct flags now.

  parent reply	other threads:[~2021-05-02  9:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93808-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug target/93808] [9 " jakub at gcc dot gnu.org
2021-04-30  8:02 ` [Bug target/93808] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-04-30  8:37 ` glaubitz at physik dot fu-berlin.de
2021-04-30 10:23 ` glaubitz at physik dot fu-berlin.de
2021-04-30 10:27 ` glaubitz at physik dot fu-berlin.de
2021-05-02  9:22 ` glaubitz at physik dot fu-berlin.de [this message]
2021-05-02  9:44 ` glaubitz at physik dot fu-berlin.de
2021-06-01  8:16 ` rguenth at gcc dot gnu.org
2022-03-22 10:37 ` rguenth at gcc dot gnu.org
2022-05-27  9:42 ` [Bug target/93808] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:39 ` jakub at gcc dot gnu.org
2023-07-07 10:36 ` [Bug target/93808] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-10-30  7:37 ` olegendo at gcc dot gnu.org
2023-10-30  7:49 ` glaubitz at physik dot fu-berlin.de

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-93808-4-ix5u1kPrA4@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).