public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimitar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113156] New: AVR build broken due to ICE while compiling libgcc, started with r14-6201-gf0a90c7d7333fc
Date: Wed, 27 Dec 2023 09:03:41 +0000 [thread overview]
Message-ID: <bug-113156-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113156
Bug ID: 113156
Summary: AVR build broken due to ICE while compiling libgcc,
started with r14-6201-gf0a90c7d7333fc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: dimitar at gcc dot gnu.org
Target Milestone: ---
AVR target build is broken after r14-6201-gf0a90c7d7333fc :
/mnt/nvme/dinux/local-workspace/gcc/libgcc/strub.c:91:1: internal compiler
error: 'global_options' are modified in local context
91 | {
| ^
0xda0b43 cl_optimization_compare(gcc_options*, gcc_options*)
/mnt/nvme/dinux/local-workspace/avr-gcc-build/gcc/options-save.cc:13414
0x94230c handle_optimize_attribute
/mnt/nvme/dinux/local-workspace/gcc/gcc/c-family/c-attribs.cc:5972
0x8224a4 decl_attributes(tree_node**, tree_node*, int, tree_node*)
/mnt/nvme/dinux/local-workspace/gcc/gcc/attribs.cc:891
0x828bad c_decl_attributes
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-decl.cc:5425
0x840acb start_function(c_declspecs*, c_declarator*, tree_node*)
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-decl.cc:10255
0x8ab355 c_parser_declaration_or_fndef
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-parser.cc:2912
0x8b663b c_parser_external_declaration
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-parser.cc:2046
0x8b7023 c_parser_translation_unit
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-parser.cc:1900
0x8b7023 c_parse_file()
/mnt/nvme/dinux/local-workspace/gcc/gcc/c/c-parser.cc:26713
0x929101 c_common_parse_file()
/mnt/nvme/dinux/local-workspace/gcc/gcc/c-family/c-opts.cc:1301
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.
make[4]: *** [/mnt/nvme/dinux/local-workspace/gcc/libgcc/static-object.mk:17:
strub.o] Error 1
next reply other threads:[~2023-12-27 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 9:03 dimitar at gcc dot gnu.org [this message]
2023-12-27 9:11 ` [Bug target/113156] " pinskia at gcc dot gnu.org
2023-12-27 9:14 ` pinskia at gcc dot gnu.org
2024-01-04 22:04 ` paulbendixen at gmail dot com
2024-01-08 14:10 ` [Bug target/113156] [14 Regression] " rguenth at gcc dot gnu.org
2024-01-10 5:08 ` pinskia at gcc dot gnu.org
2024-01-10 5:11 ` pinskia at gcc dot gnu.org
2024-01-10 5:12 ` [Bug target/113156] [11/12/13/14 " pinskia at gcc dot gnu.org
2024-01-10 5:22 ` pinskia at gcc dot gnu.org
2024-01-10 9:18 ` gjl at gcc dot gnu.org
2024-01-10 9:23 ` pinskia at gcc dot gnu.org
2024-01-10 11:18 ` gjl at gcc dot gnu.org
2024-01-11 0:13 ` pinskia at gcc dot gnu.org
2024-01-15 9:42 ` cvs-commit at gcc dot gnu.org
2024-01-15 11:43 ` cvs-commit at gcc dot gnu.org
2024-01-15 11:49 ` cvs-commit at gcc dot gnu.org
2024-01-15 13:26 ` gjl at gcc dot gnu.org
2024-01-16 22:44 ` pinskia at gcc dot gnu.org
2024-01-17 8:29 ` 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-113156-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).