public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112299] [14 Regression] Cross compiling to loongarch64-linux-gnuf64 fails because "HAVE_AS_TLS was not declared" after r14-4925-g1b30ef7cea773e Date: Thu, 22 Feb 2024 03:25:15 +0000 [thread overview] Message-ID: <bug-112299-4-5dNdkSktBR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112299-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112299 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by LuluCheng <chenglulu@gcc.gnu.org>: https://gcc.gnu.org/g:b1cad801dac215b2f594166e69759f33bd791308 commit r13-8352-gb1cad801dac215b2f594166e69759f33bd791308 Author: Xi Ruoyao <xry111@xry111.site> Date: Mon Oct 30 19:39:27 2023 +0800 LoongArch: Define HAVE_AS_TLS to 0 if it's undefined [PR112299] Now loongarch.md uses HAVE_AS_TLS, we need this to fix the failure building a cross compiler if the cross assembler is not installed yet. gcc/ChangeLog: PR target/112299 * config/loongarch/loongarch-opts.h (HAVE_AS_TLS): Define to 0 if not defined yet. (cherry picked from commit 6bf2cebe2bf49919c78814cb447d3aa6e3550d89)
prev parent reply other threads:[~2024-02-22 3:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 15:21 [Bug target/112299] New: " jamborm at gcc dot gnu.org 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 [this message]
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-5dNdkSktBR@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).