public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [pushed][PATCH v1 0/2] LoongArch: Modify the method of obtaining symbolic addresses.
Date: Tue, 26 Jul 2022 14:36:26 +0800	[thread overview]
Message-ID: <14f65155-7f20-dc23-9dbf-596e39a9cf2d@loongson.cn> (raw)
In-Reply-To: <20220719130852.2011955-1-chenglulu@loongson.cn>


在 2022/7/19 下午9:08, Lulu Cheng 写道:
> 1. The original LA macro instruction is split into two instructions to
>     obtain the address of the symbol if enable '-mexplicit-relocs'.
> 2. Currently, '-mcmodel=' only supports 'normal' mode, because other mode
>     behaviors are not yet determined. This function is gradually improved
>     by the subsequent handling.
> 3. Modify the method that calls global functions. Changed from 'la.global + jirl'
>     to 'bl'.
> 4. Some R_LARCH_64 in section .eh_frame will to generate  R_LARCH_NONE, we
>     change ASM_PREFERRED_EH_DATA_FORMAT from 'WD_EH_PE_absptr' to
>     'WD_EH_PE_pcrel | DW_EH_PE_sdata4' then relocation to R_LARCH_32_PCREL
>     from R_LARCH_64 in setction .eh_frame and not generate dynamic relocation
>     for R_LARCH_32_PCREL.
>
> This new symbol loading method not support by upstream binutils yet,
> this GCC port requires the following patches applied to binutils to build.
>
> https://sourceware.org/pipermail/binutils/2022-July/121849.html
> https://sourceware.org/pipermail/binutils/2022-July/121850.html
> https://sourceware.org/pipermail/binutils/2022-July/121851.html
> https://sourceware.org/pipermail/binutils/2022-July/121852.html
> https://sourceware.org/pipermail/binutils/2022-July/121853.html
>
> Lulu Cheng (2):
>    LoongArch: Modify the method of obtaining symbolic addresses.
>    LoongArch: Modify the definition of the ASM_PREFERRED_EH_DATA_FORMAT
>      macro.
>
>   .../config/loongarch/loongarch-common.cc      |   1 +
>   gcc/config/loongarch/constraints.md           |  24 +-
>   gcc/config/loongarch/genopts/loongarch.opt.in |   4 +
>   gcc/config/loongarch/loongarch-protos.h       |   9 +-
>   gcc/config/loongarch/loongarch.cc             | 660 +++++++++++++-----
>   gcc/config/loongarch/loongarch.h              |   4 +-
>   gcc/config/loongarch/loongarch.md             | 401 +++--------
>   gcc/config/loongarch/loongarch.opt            |   4 +
>   gcc/config/loongarch/predicates.md            |  56 +-
>   9 files changed, 629 insertions(+), 534 deletions(-)
>


      parent reply	other threads:[~2022-07-26  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 13:08 [PATCH " Lulu Cheng
2022-07-19 13:08 ` [PATCH v1 1/2] " Lulu Cheng
2022-07-19 14:29   ` Xi Ruoyao
2022-07-20  0:40     ` Lulu Cheng
2022-07-19 13:08 ` [PATCH v1 2/2] LoongArch: Modify the definition of the ASM_PREFERRED_EH_DATA_FORMAT macro Lulu Cheng
2022-07-26  6:36 ` Lulu Cheng [this message]

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=14f65155-7f20-dc23-9dbf-596e39a9cf2d@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).