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: Chenghua Xu <xuchenghua@loongson.cn>,
	Youling Tang <tangyouling@loongson.cn>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jinyang He <hejinyang@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: LoongArch: add model attribute
Date: Wed, 24 Aug 2022 14:54:41 +0800	[thread overview]
Message-ID: <9e762c7d-5cbd-7e6e-9610-cd3806ded90f@loongson.cn> (raw)
In-Reply-To: <fc317f3943c4ea7810ccf532707c6a3255ecd3a0.camel@xry111.site>


在 2022/8/23 下午10:51, Xi Ruoyao 写道:
> diff --git a/gcc/config/loongarch/loongarch-protos.h b/gcc/config/loongarch/loongarch-protos.h
> index cadaad7519c..4e925aa3876 100644
> --- a/gcc/config/loongarch/loongarch-protos.h
> +++ b/gcc/config/loongarch/loongarch-protos.h
> @@ -30,6 +30,12 @@ along with GCC; see the file COPYING3.  If not see
>      SYMBOL_PCREL
>          The symbol's value will be loaded directly from data section.
>   
> +   SYMBOL_PCREL32
> +   SYMBOL_PCREL64
> +       Like SYMBOL_PCREL, but the PC-relative offset of the symbol is
> +       assumed to be in the ± 2GiB or ± 8 EiB range, instead of the
> +       code model specification.
> +
>      SYMBOL_TLS
>          A thread-local symbol.
>   

I don't think it's necessary to add SYMBOL_PCREL32, SYMBOL_PCREL can 
represent relative pc operation in normal mode.


WARNING: multiple messages have this Message-ID

From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Chenghua Xu <xuchenghua@loongson.cn>,
	Youling Tang <tangyouling@loongson.cn>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jinyang He <hejinyang@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: LoongArch: add model attribute
Date: Wed, 24 Aug 2022 14:54:41 +0800	[thread overview]
Message-ID: <9e762c7d-5cbd-7e6e-9610-cd3806ded90f@loongson.cn> (raw)
Message-ID: <20220824065441.Sfmo7VZbE5NAN1poM8iqnRpEPb3370Q3xkcFgiPDJfM@z> (raw)
In-Reply-To: <fc317f3943c4ea7810ccf532707c6a3255ecd3a0.camel@xry111.site>

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]


在 2022/8/23 下午10:51, Xi Ruoyao 写道:
> diff --git a/gcc/config/loongarch/loongarch-protos.h b/gcc/config/loongarch/loongarch-protos.h
> index cadaad7519c..4e925aa3876 100644
> --- a/gcc/config/loongarch/loongarch-protos.h
> +++ b/gcc/config/loongarch/loongarch-protos.h
> @@ -30,6 +30,12 @@ along with GCC; see the file COPYING3.  If not see
>      SYMBOL_PCREL
>          The symbol's value will be loaded directly from data section.
>   
> +   SYMBOL_PCREL32
> +   SYMBOL_PCREL64
> +       Like SYMBOL_PCREL, but the PC-relative offset of the symbol is
> +       assumed to be in the ± 2GiB or ± 8 EiB range, instead of the
> +       code model specification.
> +
>      SYMBOL_TLS
>          A thread-local symbol.
>   

I don't think it's necessary to add SYMBOL_PCREL32, SYMBOL_PCREL can 
represent relative pc operation in normal mode.


  reply	other threads:[~2022-08-24  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 14:51 Xi Ruoyao
2022-08-24  6:54 ` Lulu Cheng [this message]
2022-08-24  6:54   ` Lulu Cheng
2022-08-30 13:42 ` Richard Sandiford

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=9e762c7d-5cbd-7e6e-9610-cd3806ded90f@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hejinyang@loongson.cn \
    --cc=i@xen0n.name \
    --cc=tangyouling@loongson.cn \
    --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).