public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "miro.kropacek at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112712] New: Crash when compiling g++ -m68020-60 -O2
Date: Sat, 25 Nov 2023 23:29:14 +0000 [thread overview]
Message-ID: <bug-112712-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112712
Bug ID: 112712
Summary: Crash when compiling g++ -m68020-60 -O2
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: miro.kropacek at gmail dot com
Target Milestone: ---
Created attachment 56688
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56688&action=edit
Preprocessed output
This is a crash which seems to be specific to the -m68020-60 option (or better
said to 060 code generation as the only other option where this bugs occurs is
-m68060). When changing to any other CPU (-m68000, -mcpu=5475, ...) and/or
changing to -O1, -O0, ... everything is fine.
See the attached preprocessed file which triggers the bug:
m68k-elf-g++ -c -g -O2 -m68020-60 -fomit-frame-pointer -funsigned-char
-std=gnu++20 -fvisibility=hidden -Wno-sign-compare crash.cpp
similar/main/multi.cpp:6167:1: internal compiler error: in push_reload, at
reload.cc:1124
6167 | }
| ^
0x15fee77 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char
const*, __va_list_tag (*) [1], diagnostic_t)
???:0
0x15ffd3c internal_error(char const*, ...)
???:0
0x5e9465 fancy_abort(char const*, int, char const*)
???:0
0x5c9a9d push_reload(rtx_def*, rtx_def*, rtx_def**, rtx_def**, reg_class,
machine_mode, machine_mode, int, int, int, reload_type) [clone .cold]
???:0
0xca2ffb find_reloads(rtx_insn*, int, int, int, short*)
???:0
0xcb0dcb reload(rtx_insn*, int)
???:0
0xb4657a (anonymous namespace)::pass_reload::execute(function*)
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2023-11-25 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 23:29 miro.kropacek at gmail dot com [this message]
2023-11-26 13:53 ` [Bug target/112712] " mikpelinux at gmail dot com
2023-11-27 8:07 ` rguenth at gcc dot gnu.org
2023-11-27 21:12 ` mikpelinux at gmail dot com
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-112712-4@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).