public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112299] New: Cross compiling to loongarch64-linux-gnuf64 fails because "HAVE_AS_TLS was not declared" after r14-4925-g1b30ef7cea773e Date: Mon, 30 Oct 2023 15:21:55 +0000 [thread overview] Message-ID: <bug-112299-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112299 Bug ID: 112299 Summary: Cross compiling to loongarch64-linux-gnuf64 fails because "HAVE_AS_TLS was not declared" after r14-4925-g1b30ef7cea773e Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org CC: chenxiaolong at loongson dot cn Target Milestone: --- Host: x86_64-linux-gnu Target: loongarch64-linux-gnuf64 Starting with r14-4925-g1b30ef7cea773e, when I try to test that cross compilation to target loongarch64-linux-gnuf64 still works by configuring gcc with: $ ../src/configure --target=loongarch64-linux-gnuf64 --disable-bootstrap --enable-languages=c,c++ --disable-multilib --enable-obsolete and then building just the compiler with: $ make -j64 all-host CXXFLAGS="-O0 -g" CFLAGS="-O0 -g" The compilation fails with: ../../src/gcc/config/loongarch/loongarch.md:3655:2: error: ‘HAVE_AS_TLS’ was not declared in this scope 3655 | "HAVE_AS_TLS" | ^~~~~~~~~~~ config.status: executing libtool commands ../../src/gcc/config/loongarch/loongarch.md:3655:2: error: ‘HAVE_AS_TLS’ was not declared in this scope 3655 | "HAVE_AS_TLS" | ^~~~~~~~~~~ ../../src/gcc/config/loongarch/loongarch.md:3655:2: error: ‘HAVE_AS_TLS’ was not declared in this scope 3655 | "HAVE_AS_TLS" | ^~~~~~~~~~~ ../../src/gcc/config/loongarch/loongarch.md:3655:2: error: ‘HAVE_AS_TLS’ was not declared in this scope 3655 | "HAVE_AS_TLS" | ^~~~~~~~~~~ make[1]: *** [Makefile:2958: build/gencondmd.o] Error 1 make[1]: *** Waiting for unfinished jobs.... rm gfdl.pod gcc.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod cpp.pod gcov.pod lto-dump.pod make[1]: Leaving directory '/home/mjambor/gcc/mine/obj/gcc' According to our buildbot, building a cross for loongarch64-linux-gnuf32 and loongarch64-linux-gnusf also fails, likely because of the same issue.
next reply other threads:[~2023-10-30 15:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 15:21 jamborm at gcc dot gnu.org [this message] 2023-10-30 19:41 ` [Bug target/112299] " pinskia at gcc dot gnu.org 2023-10-30 19:43 ` [Bug target/112299] [14 Regression] " pinskia at gcc dot gnu.org 2023-10-31 6:03 ` xry111 at gcc dot gnu.org 2023-10-31 6:24 ` cvs-commit at gcc dot gnu.org 2023-10-31 6:25 ` xry111 at gcc dot gnu.org 2024-02-22 3:17 ` cvs-commit at gcc dot gnu.org 2024-02-22 3:25 ` cvs-commit 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-112299-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: linkBe 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).