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:23:22 +0000 [thread overview]
Message-ID: <bug-112330-4-YgNDVq0fEN@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 #6 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to chenglulu from comment #5)
> (In reply to Xi Ruoyao from comment #4)
> > (In reply to chenglulu from comment #3)
> > > (In reply to Xi Ruoyao from comment #1)
> > > > (In reply to Xi Ruoyao from comment #0)
> > > >
> > > > > I guess the easiest solution is raising the minimal GAS requirement of
> > > > > bootstrapping GCC 14 on LoongArch to 2.42.
> > > >
> > > > Another solution might be default to -mno-relax if GAS is 2.41, but I'm not
> > > > sure if it's enough.
> > >
> > > This issue really doesn't happen after adding -mno-relax, but is it really
> > > necessary to judge the version of binutils because of this?
> >
> > I'm not sure if -mno-relax is the proper fix. For now I've reduced the test
> > case to:
> >
> > a:
> > .rept 100000
> > nop
> > .endr
> > beq $r12, $r13, a
> >
> > but this still does not work with GAS 2.41 even if -mno-relax.
>
> If this is the assembly code compiled by gcc, then I think it's a gcc bug,
> although AS shouldn't be an internal error.
The internal error issue is fixed by Binutils commit
f87cf663af71e5d78c8d647fa48562102f3b0615.
I think I've over-simplified the test case. GCC does not generate something
like this.
next prev parent reply other threads:[~2023-11-01 9:23 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 [this message]
2023-11-01 9:33 ` chenglulu at loongson dot cn
2023-11-01 9:56 ` xry111 at gcc dot gnu.org
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-YgNDVq0fEN@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).