public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112330] [14 Regression] LoongArch: LTO bootstrap failure with GAS 2.41
Date: Wed, 01 Nov 2023 09:56:58 +0000	[thread overview]
Message-ID: <bug-112330-4-Qkv79zhweW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112330-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330

--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to chenglulu from comment #7)

> Uh, I also thought about this gcc and binutils matching issue when I
> submitted r14-4674, but I didn't think about whether this should be solved?
> How to fix it？

I'm not sure either.

The easiest way is just claiming we need Binutils 2.42 for GCC 14 (documenting
this in "Host/target specific installation notes for GCC", install.texi).

If we want to maintain the compatibility with 2.41, I think the best solution
would be probing the capability of GAS and disable relaxation by default if
necessary.

There is already another issue breaking relaxation with Binutils 2.41 anyway:
https://sourceware.org/bugzilla/show_bug.cgi?id=30944. Mengqinggang has posted
a fix at https://sourceware.org/pipermail/binutils/2023-October/129941.html but
it's still under testing. Hopefully the fix will be committed before Binutils
2.42 freeze.

  parent reply	other threads:[~2023-11-01  9:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  8:38 [Bug target/112330] New: " xry111 at gcc dot gnu.org
2023-11-01  8:42 ` [Bug target/112330] " xry111 at gcc dot gnu.org
2023-11-01  8:54 ` xry111 at gcc dot gnu.org
2023-11-01  9:00 ` chenglulu at loongson dot cn
2023-11-01  9:07 ` xry111 at gcc dot gnu.org
2023-11-01  9:10 ` chenglulu at loongson dot cn
2023-11-01  9:23 ` xry111 at gcc dot gnu.org
2023-11-01  9:33 ` chenglulu at loongson dot cn
2023-11-01  9:56 ` xry111 at gcc dot gnu.org [this message]
2023-11-01  9:58 ` [Bug target/112330] [14 Regression] LoongArch: Bootstrap " xry111 at gcc dot gnu.org
2023-11-02  6:57 ` chenglulu at loongson dot cn
2023-11-02  7:43 ` xry111 at gcc dot gnu.org
2023-11-02  7:59 ` chenglulu at loongson dot cn
2023-11-02  8:07 ` xry111 at gcc dot gnu.org
2023-11-02  8:43 ` chenglulu at loongson dot cn
2023-11-02  9:54 ` rguenth at gcc dot gnu.org
2023-11-02 11:41 ` [Bug target/112330] [14 Regression] LoongArch: Outputted .align directive may trigger assembler error " xry111 at gcc dot gnu.org
2023-11-14  9:37 ` cvs-commit at gcc dot gnu.org
2023-11-14  9:47 ` 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-112330-4-Qkv79zhweW@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).