public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Levente <leventelist@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Can't compile GCC-14 for AVR
Date: Mon, 15 Jan 2024 00:19:13 +0100	[thread overview]
Message-ID: <967ecf57-2f9a-4a1b-88e2-1f0e57483a39@gmail.com> (raw)

I'm trying to set up a toolchain for avr-dd MCUs, and I get this error 
message when I try to compile gcc:


/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/./gcc/xgcc 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/./gcc/ 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/bin/ 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/lib/ 
-isystem 
/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/include 
-isystem 
/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/sys-include 
    -g -O2 -mdouble=64 -O2  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE 
-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes 
-Wmissing-prototypes -Wold-style-definition  -isystem ./include 
-Dinhibit_libc -mcall-prologues -Os -g -DIN_LIBGCC2 -fbuilding-libgcc 
-fno-stack-protector -Dinhibit_libc -Dinhibit_libc -mcall-prologues -Os 
-I. -I. -I../../.././gcc -I../../../../libgcc -I../../../../libgcc/. 
-I../../../../libgcc/../gcc -I../../../../libgcc/../include 
-DHAVE_CC_TLS -DUSE_EMUTLS  -o hardcfr.o -MT hardcfr.o -MD -MP -MF 
hardcfr.dep  -c ../../../../libgcc/hardcfr.c -fvisibility=hidden 
-DHIDE_EXPORTS
/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/./gcc/xgcc 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/./gcc/ 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/bin/ 
-B/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/lib/ 
-isystem 
/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/include 
-isystem 
/home/lev/git/library/software/scripts/avr_toolchain_build/out/avr/sys-include 
    -g -O2 -mdouble=64 -O2  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE 
-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes 
-Wmissing-prototypes -Wold-style-definition  -isystem ./include 
-Dinhibit_libc -mcall-prologues -Os -g -DIN_LIBGCC2 -fbuilding-libgcc 
-fno-stack-protector -Dinhibit_libc -Dinhibit_libc -mcall-prologues -Os 
-I. -I. -I../../.././gcc -I../../../../libgcc -I../../../../libgcc/. 
-I../../../../libgcc/../gcc -I../../../../libgcc/../include 
-DHAVE_CC_TLS -DUSE_EMUTLS  -o strub.o -MT strub.o -MD -MP -MF strub.dep 
  -c ../../../../libgcc/strub.c -fvisibility=hidden -DHIDE_EXPORTS
../../../../libgcc/strub.c:95:1: internal compiler error: 
'global_options' are modified in local context
    95 | {
       | ^
0xdc6e93 cl_optimization_compare(gcc_options*, gcc_options*)
	/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/gcc/options-save.cc:13442
0x96537c handle_optimize_attribute
	../../gcc/c-family/c-attribs.cc:5983
0x840c04 decl_attributes(tree_node**, tree_node*, int, tree_node*)
	../../gcc/attribs.cc:905
0x847559 c_decl_attributes
	../../gcc/c/c-decl.cc:5495
0x85f4db start_function(c_declspecs*, c_declarator*, tree_node*)
	../../gcc/c/c-decl.cc:10433
0x8cb731 c_parser_declaration_or_fndef
	../../gcc/c/c-parser.cc:2912
0x8d6873 c_parser_external_declaration
	../../gcc/c/c-parser.cc:2046
0x8d72b3 c_parser_translation_unit
	../../gcc/c/c-parser.cc:1900
0x8d72b3 c_parse_file()
	../../gcc/c/c-parser.cc:26815
0x94bf11 c_common_parse_file()
	../../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]: *** [../../../../libgcc/static-object.mk:17: strub.o] Error 1
make[4]: Leaving directory 
'/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/avr/double64/libgcc'
make[3]: *** [Makefile:1221: multi-do] Error 1
make[3]: Leaving directory 
'/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/avr/libgcc'
make[2]: *** [Makefile:127: all-multi] Error 2
make[2]: Leaving directory 
'/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr/avr/libgcc'
make[1]: *** [Makefile:13076: all-target-libgcc] Error 2
make[1]: Leaving directory 
'/home/lev/git/library/software/scripts/avr_toolchain_build/gcc/obj-avr'
make: *** [Makefile:1039: all] Error 2


This is with the current HEAD of master branch.
I'm on a Debian stable, my host gcc is gcc-12.
My binutils is gdb-14.1-release.

My configure options are:
--target=avr
         --enable-languages=c,c++
         --disable-nls
         --disable-libssp
         --disable-libada
         --with-dwarf2
         --disable-shared
         --enable-static
         --enable-mingw-wildcard
         --enable-plugin
         --with-gnu-as


What do I do wrong?


Thanks,
Lev


-- 
Levente Kovacs
Senior Electronic Engineer

W: http://levente.logonex.eu

             reply	other threads:[~2024-01-14 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 23:19 Levente [this message]
2024-01-15  6:09 ` Xi Ruoyao
2024-01-15  9:50 ` [patch,avr,applied] Fix PR target/113156 - ICE when building libgcc Georg-Johann Lay
2024-01-15 11:55   ` Levente

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=967ecf57-2f9a-4a1b-88e2-1f0e57483a39@gmail.com \
    --to=leventelist@gmail.com \
    --cc=gcc-help@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).