public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: LuluCheng <chenglulu@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-10172] LoongArch: Define HAVE_AS_TLS to 0 if it's undefined [PR112299]
Date: Thu, 22 Feb 2024 03:17:07 +0000 (GMT)	[thread overview]
Message-ID: <20240222031707.77A083858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:09de4b6b22bd66dacdade65ce633f29f302363b5

commit r12-10172-g09de4b6b22bd66dacdade65ce633f29f302363b5
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)

Diff:
---
 gcc/config/loongarch/loongarch-opts.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gcc/config/loongarch/loongarch-opts.h b/gcc/config/loongarch/loongarch-opts.h
index bdf79ecc193c..b4115dd7f85f 100644
--- a/gcc/config/loongarch/loongarch-opts.h
+++ b/gcc/config/loongarch/loongarch-opts.h
@@ -95,4 +95,8 @@ loongarch_config_target (struct loongarch_target *target,
 #define HAVE_AS_COND_BRANCH_RELAXATION 0
 #endif
 
+#ifndef HAVE_AS_TLS
+#define HAVE_AS_TLS 0
+#endif
+
 #endif /* LOONGARCH_OPTS_H */

                 reply	other threads:[~2024-02-22  3:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240222031707.77A083858D37@sourceware.org \
    --to=chenglulu@gcc.gnu.org \
    --cc=gcc-cvs@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).