public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: chenglulu <chenglulu@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn
Subject: Re:[pushed] [PATCH] LoongArch: Disable TLS type symbols from generating non-zero offsets.
Date: Thu, 25 Jan 2024 15:38:47 +0800	[thread overview]
Message-ID: <d50b8262-a0c9-34d0-4518-3f6c0f515cee@loongson.cn> (raw)
In-Reply-To: <20240123035435.1402-1-chenglulu@loongson.cn>

Pushed to r14-8412.

在 2024/1/23 上午11:54, Lulu Cheng 写道:
> TLS gd ld and ie type symbols will generate corresponding GOT entries,
> so non-zero offsets cannot be generated.
> The address of TLS le type symbol+addend is not implemented in binutils,
> so non-zero offset is not generated here for the time being.
>
> gcc/ChangeLog:
>
> 	* config/loongarch/loongarch.cc (loongarch_symbolic_constant_p):
> 	For symbols of type tls, non-zero Offset is not generated.
> ---
>   gcc/config/loongarch/loongarch.cc | 18 +++++++++---------
>   1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/gcc/config/loongarch/loongarch.cc b/gcc/config/loongarch/loongarch.cc
> index 82467474288..f2ce1f6906d 100644
> --- a/gcc/config/loongarch/loongarch.cc
> +++ b/gcc/config/loongarch/loongarch.cc
> @@ -1924,11 +1924,7 @@ loongarch_symbolic_constant_p (rtx x, enum loongarch_symbol_type *symbol_type)
>         x = UNSPEC_ADDRESS (x);
>       }
>     else if (SYMBOL_REF_P (x) || LABEL_REF_P (x))
> -    {
> -      *symbol_type = loongarch_classify_symbol (x);
> -      if (*symbol_type == SYMBOL_TLS)
> -	return true;
> -    }
> +    *symbol_type = loongarch_classify_symbol (x);
>     else
>       return false;
>   
> @@ -1939,17 +1935,21 @@ loongarch_symbolic_constant_p (rtx x, enum loongarch_symbol_type *symbol_type)
>        relocations.  */
>     switch (*symbol_type)
>       {
> -    case SYMBOL_TLS_IE:
> -    case SYMBOL_TLS_LE:
> -    case SYMBOL_TLSGD:
> -    case SYMBOL_TLSLDM:
>       case SYMBOL_PCREL:
>       case SYMBOL_PCREL64:
>         /* GAS rejects offsets outside the range [-2^31, 2^31-1].  */
>         return sext_hwi (INTVAL (offset), 32) == INTVAL (offset);
>   
> +    /* The following symbol types do not allow non-zero offsets.  */
>       case SYMBOL_GOT_DISP:
> +    case SYMBOL_TLS_IE:
> +    case SYMBOL_TLSGD:
> +    case SYMBOL_TLSLDM:
>       case SYMBOL_TLS:
> +    /* From an implementation perspective, tls_le symbols are allowed to
> +       have non-zero offsets, but currently binutils has not added support,
> +       so the generation of non-zero offsets is prohibited here.  */
> +    case SYMBOL_TLS_LE:
>         return false;
>       }
>     gcc_unreachable ();


      reply	other threads:[~2024-01-25  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  3:54 Lulu Cheng
2024-01-25  7:38 ` chenglulu [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=d50b8262-a0c9-34d0-4518-3f6c0f515cee@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).