public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: xuchenghua@loongson.cn, Wang Xuerui <i@xen0n.name>
Subject: Re: [PATCH][wwwdocs] gcc-13: Add loongarch '-mexplicit-relocs' support
Date: Tue, 26 Jul 2022 19:42:59 +0800	[thread overview]
Message-ID: <93f7b58a-d7a7-543a-21e1-19d237593426@loongson.cn> (raw)
In-Reply-To: <25a7d2fcac8194083e58ed960eaf0f42dafc0559.camel@xry111.site>


在 2022/7/26 下午5:44, Xi Ruoyao 写道:
>
>> +  whether the <code>la.*</code> macro instructions will be generated when
>> +  loading symbolic addresses.
>> +  This feature requires binutils version 2.40 or later. If you want to use the
>> +  older version of bintuils, add compiler parameters
>> +  <code>-mno-explicit-relocs</code> at compile time.
> Does it mean we need to make sure GCC 13 released after binutils-2.40?
> binutils-2.39 release branch is already created and it's now explicitly
> "no new feature" so a backport seems impossible...

Do you think it's okay if we don't write Binutils version restrictions 
now and wait until Binutils code is released to annotate?

>> +  </li>
>> +  <li>The method for calling global functions changed from
>> +  <code>la.global + jirl</code> to <code>bl</code> when complied add
>> +  <code>-fplt</code>.
> "from la.global + jirl to bl with -fno-plt and -mexplicit-relocs"?  With
> "-fplt" GCC 12 is already using bl, and with -mno-explicit-relocs
> la.global is still used (if I read func-call-3.c correctly).
I  should put '-fplt -mexplicit-relocs' here.
>> +  <li>Changed <code>ASM_PREFERRED_EH_DATA_FORMAT</code> macro definition from
>> +  <code>WD_EH_PE_absptr</code> to <code>WD_EH_PE_pcrel | DW_EH_PE_sdata4</code>.
>> +  </li>
> I don't think this paragraph is necessary because this change is purely
> internal.
>
Should we indicate that our .eh_frame section format has changed?


Thanks!


  reply	other threads:[~2022-07-26 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  7:21 Lulu Cheng
2022-07-26  9:44 ` Xi Ruoyao
2022-07-26 11:42   ` Lulu Cheng [this message]
2022-07-26 12:01     ` Xi Ruoyao
2022-07-26 13:26       ` Lulu Cheng
2022-07-26 14:15         ` [PATCH] LoongArch: adjust the default of -mexplicit-relocs by checking gas feature Xi Ruoyao
2022-07-27  1:34           ` Lulu Cheng
2022-07-27  2:22             ` Xi Ruoyao
2022-07-28  2:59       ` [PATCH][wwwdocs] gcc-13: Add loongarch '-mexplicit-relocs' support Lulu Cheng
2022-07-28 10:41         ` Xi Ruoyao
2022-07-28 13:06           ` Lulu Cheng
2022-07-26 11:32 ` Gerald Pfeifer
2022-07-26 12:28   ` Lulu Cheng

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=93f7b58a-d7a7-543a-21e1-19d237593426@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).