From: mengqinggang <mengqinggang@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, chenglulu <chenglulu@loongson.cn>,
gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: gcc: Modify gas uleb128 support test.
Date: Fri, 15 Sep 2023 11:59:55 +0800 [thread overview]
Message-ID: <36c12d6f-8834-45e5-8703-f74fb2e44063@loongson.cn> (raw)
In-Reply-To: <20b526e66be657eae37f5b2c68e4efee442cef62.camel@xry111.site>
Thank you very much, we will send a new patch use this.
在 2023/9/14 下午8:09, Xi Ruoyao 写道:
> On Thu, 2023-09-14 at 19:54 +0800, chenglulu wrote:
>> Sorry, it's my problem. We will modify it as soon as possible.
> Try this:
>
> diff --git a/gcc/configure.ac b/gcc/configure.ac
> index cb4be11facd..10027a4aaaa 100644
> --- a/gcc/configure.ac
> +++ b/gcc/configure.ac
> @@ -3229,10 +3229,18 @@ AC_MSG_RESULT($gcc_cv_ld_ro_rw_mix)
>
> gcc_AC_INITFINI_ARRAY
>
> +# Some assemblers (GNU as for LoongArch) generates relocations for
> +# leb128 symbol arithmetic for relaxation, we need to disable relaxation
> +# probing leb128 support then.
> +gcc_GAS_CHECK_FEATURE([-mno-relax support],
> + gcc_cv_as_mno_relax,[-mno-relax],[.text],,
> + [check_leb128_asflags=-mno-relax])
> +
> # Check if we have .[us]leb128, and support symbol arithmetic with it.
> # Older versions of GAS and some non-GNU assemblers, have a bugs handling
> # these directives, even when they appear to accept them.
> -gcc_GAS_CHECK_FEATURE([.sleb128 and .uleb128], gcc_cv_as_leb128,,
> +gcc_GAS_CHECK_FEATURE([.sleb128 and .uleb128], gcc_cv_as_leb128,
> +[$check_leb128_asflags],
> [ .data
> .uleb128 L2 - L1
> L1:
>
>
>
prev parent reply other threads:[~2023-09-15 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 11:21 Lulu Cheng
2023-09-14 11:45 ` Xi Ruoyao
2023-09-14 11:54 ` chenglulu
2023-09-14 12:09 ` Xi Ruoyao
2023-09-15 3:59 ` mengqinggang [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=36c12d6f-8834-45e5-8703-f74fb2e44063@loongson.cn \
--to=mengqinggang@loongson.cn \
--cc=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).