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/110934] m68k: ICE with -fzero-call-used-regs=all compiling openssh 9.3p2
Date: Wed, 20 Dec 2023 03:40:08 +0000 [thread overview]
Message-ID: <bug-110934-4-3CaYJQ1Q9A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110934-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110934
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2023-08-07 00:00:00 |2023-12-20
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #5 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Mikael Pettersson from comment #4)
> I can reproduce with m68k-unknown-linux-gnu-gcc -Os
> -fzero-call-used-regs=all -fPIC.
Hence confirmed.
next prev parent reply other threads:[~2023-12-20 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 11:33 [Bug c/110934] New: " wbx at openadk dot org
2023-08-07 12:03 ` [Bug rtl-optimization/110934] " rguenth at gcc dot gnu.org
2023-08-07 12:07 ` wbx at openadk dot org
2023-08-07 12:07 ` wbx at openadk dot org
2023-08-07 14:52 ` [Bug target/110934] " pinskia at gcc dot gnu.org
2023-08-07 16:41 ` mikpelinux at gmail dot com
2023-12-20 3:40 ` sjames at gcc dot gnu.org [this message]
2023-12-27 22:15 ` mikpelinux at gmail dot com
2023-12-28 13:44 ` mikpelinux at gmail dot com
2023-12-28 17:38 ` mikpelinux at gmail dot com
2023-12-28 18:01 ` mikpelinux at gmail dot com
2023-12-28 20:39 ` pinskia at gcc dot gnu.org
2024-01-04 16:13 ` mikpelinux at gmail dot com
2024-01-18 16:43 ` mikpelinux at gmail dot com
2024-01-19 23:24 ` cvs-commit at gcc dot gnu.org
2024-01-19 23:25 ` law at gcc dot gnu.org
2024-01-25 6:24 ` sjames at gcc dot gnu.org
2024-03-16 0:09 ` pinskia at gcc dot gnu.org
2024-03-25 13:26 ` sjames 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-110934-4-3CaYJQ1Q9A@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).