public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chenglulu at loongson dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112330] [14 Regression] LoongArch: Bootstrap failure with GAS 2.41
Date: Thu, 02 Nov 2023 08:43:34 +0000	[thread overview]
Message-ID: <bug-112330-4-Q8FCV5g0JF@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 #14 from chenglulu <chenglulu at loongson dot cn> ---
(In reply to Xi Ruoyao from comment #13)
> (In reply to chenglulu from comment #12)
> > (In reply to Xi Ruoyao from comment #11)
> > > I cherry-picked f87cf663af71e5d78c8d647fa48562102f3b0615 for Binutils 2.41
> > > and get some better error message:
> > > 
> > > t.s:98064: Error: Reloc overflow
> > > t.s:101127: Error: Reloc overflow
> > > t.s:101453: Error: Reloc overflow
> > > t.s:101555: Error: Reloc overflow
> > > 
> > > t.s is the assembly file in attachments.
> > 
> > 1fb3cdd87ec61715a5684925fb6d6a6cf53bb97c is also required．
> 
> I know, I'm just trying to understand the issue better.
> 
> I don't really understand why this was not a problem before r14-4674.  And
> this issue also did not show up immediately after r14-4674 (it even did not
> show up when I was developing r14-4851).


We can clearly delete the macro ASM_OUTPUT_ALIGN_WITH_NOP in r14-4674, and
before deleting this macro, the generated assembly file looks like this:

...
   .align 16,54525952,4
.L1:
...
   blt  $r12,$r13,.L１
...

after:

   .align 16
.L1:
...
   blt $r12,$r13,.L1
...

First of all, if you add -mrelax during the assembly process,".align
16,54525952,4" will be based on the situation at the time of assembly, and the
choice is to insert a nop function without insertion.But this ".align 16" will
insert 3 nops unconditionally. When calculating the jump range of the
conditional branch, gcc calculates the space required for .align according to
the actual alignment.
So after r14-4674 there will be an error．

  parent reply	other threads:[~2023-11-02  8:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  8:38 [Bug target/112330] New: [14 Regression] LoongArch: LTO bootstrap " 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
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 [this message]
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-Q8FCV5g0JF@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).