public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "triffid.hunter at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105753] [avr] ICE: in add_clobbers, at config/avr/avr-dimode.md:2705
Date: Sun, 11 Sep 2022 10:19:41 +0000 [thread overview]
Message-ID: <bug-105753-4-YsY755QrvA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105753-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105753
Triffid Hunter <triffid.hunter at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |triffid.hunter at gmail dot com
--- Comment #5 from Triffid Hunter <triffid.hunter at gmail dot com> ---
Created attachment 53561
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53561&action=edit
patch based on comment 1
I ran into this issue yesterday (with gcc-13.0.0-20220904).
I made the attached patch based on Comment 1, and it does seem to solve the
issue.
I had some odd lto-related crashes afterwards, but wasn't able to reproduce
them after a clean rebuild of my project - so I suspect there was some odd
interaction with stale/cached object files.
lto crash backtrace in case it's relevant:
avr-gcc -Wall -Wextra -Os -g -flto -fuse-linker-plugin -Wl,--gc-sections
-mmcu=atmega2560 -fno-stack-protector -o
/tmp/arduino_build_820599/sketch_sep10a.ino.elf
/tmp/arduino_build_820599/sketch/sketch_sep10a.ino.cpp.o
/tmp/arduino_build_820599/libraries/SD/File.cpp.o
/tmp/arduino_build_820599/libraries/SD/SD.cpp.o
/tmp/arduino_build_820599/libraries/SD/utility/Sd2Card.cpp.o
/tmp/arduino_build_820599/libraries/SD/utility/SdFile.cpp.o
/tmp/arduino_build_820599/libraries/SD/utility/SdVolume.cpp.o
/tmp/arduino_build_820599/libraries/SPI/SPI.cpp.o
/tmp/arduino_build_820599/../arduino_cache_495395/core/core_arduino_avr_mega_cpu_atmega2560_0535ac2d4e0500949a67f524c7f20d71.a
-L/tmp/arduino_build_820599 -lm
lto1: internal compiler error: Segmentation fault
0x135b2a8 internal_error(char const*, ...)
???:0
0x675125 bp_unpack_string(data_in*, bitpack_d*)
???:0
0x986c9e cl_optimization_stream_in(data_in*, bitpack_d*, cl_optimization*)
???:0
0xc3bf60 streamer_read_tree_bitfields(lto_input_block*, data_in*, tree_node*)
???:0
0x904fad lto_input_tree_1(lto_input_block*, data_in*, LTO_tags, unsigned int)
???:0
0x9053d7 lto_input_scc(lto_input_block*, data_in*, unsigned int*, unsigned
int*, bool)
???:0
0x5e9fc8 read_cgraph_and_symbols(unsigned int, char const**)
???:0
0x5d7222 lto_main()
???:0
Note: stopped happening after clean project rebuild, but ideally it should
throw a proper error rather than a segfault?
next prev parent reply other threads:[~2022-09-11 10:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 22:35 [Bug target/105753] New: " filip.hejsek at gmail dot com
2022-05-28 2:55 ` [Bug target/105753] " filip.hejsek at gmail dot com
2022-06-04 22:19 ` pinskia at gcc dot gnu.org
2022-06-12 23:41 ` filip.hejsek at gmail dot com
2022-06-12 23:48 ` pinskia at gcc dot gnu.org
2022-09-11 10:19 ` triffid.hunter at gmail dot com [this message]
2022-09-25 21:45 ` pinskia at gcc dot gnu.org
2022-10-02 8:06 ` rainer-gcc at wwad dot de
2022-12-09 14:26 ` fiesh at zefix dot tv
2022-12-09 14:31 ` fiesh at zefix dot tv
2023-01-25 18:45 ` user99627 at gmx dot com
2023-01-25 19:39 ` user99627 at gmx dot com
2023-01-31 23:26 ` user99627 at gmx dot com
2023-02-01 7:48 ` fiesh at zefix dot tv
2023-02-01 10:36 ` user99627 at gmx dot com
2023-04-20 19:55 ` gjl at gcc dot gnu.org
2023-04-20 20:40 ` [Bug rtl-optimization/105753] " gjl at gcc dot gnu.org
2023-04-21 7:47 ` gjl at gcc dot gnu.org
2023-04-21 9:00 ` gjl at gcc dot gnu.org
2023-04-23 10:58 ` gjl at gcc dot gnu.org
2023-05-20 5:53 ` cvs-commit at gcc dot gnu.org
2023-05-20 6:20 ` cvs-commit at gcc dot gnu.org
2023-05-20 6:35 ` cvs-commit at gcc dot gnu.org
2023-05-20 6:46 ` gjl 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-105753-4-YsY755QrvA@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).