From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn,
mengqinggang <mengqinggang@loongson.cn>
Subject: Re: [PATCH] LoongArch: gcc: Modify gas uleb128 support test.
Date: Thu, 14 Sep 2023 19:45:18 +0800 [thread overview]
Message-ID: <1c315fdbb63b5f5eb5ff86c0b6989fccba9b5658.camel@xry111.site> (raw)
In-Reply-To: <20230914112102.10247-1-chenglulu@loongson.cn>
On Thu, 2023-09-14 at 19:21 +0800, Lulu Cheng wrote:
> diff --git a/gcc/configure.ac b/gcc/configure.ac
> index 09082e8ccae..072fe1d2b48 100644
> --- a/gcc/configure.ac
> +++ b/gcc/configure.ac
> @@ -3226,6 +3226,19 @@ L2:
> .uleb128 0x8000000000000000
> ],
> [[
> +case "$target" in
> + loongarch*-*-*)
> + if test "x$gcc_cv_ld" != x; then
> + ac_try='$gcc_cv_ld conftest.o -o conftest -e 0x0 >&5'
> + { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$ac_try\""; } >&5
> + (eval $ac_try) 2>&5
> + ac_status=$?
> + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
> + test $ac_status = 0
> + mv conftest conftest.o
> + fi
> +esac
Phew. Randomly modifying configure and paste the modification into
configure.ac is not the correct way to modify configure.ac.
ac_* are autoconf internal names so we cannot use them.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-09-14 11:45 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 [this message]
2023-09-14 11:54 ` chenglulu
2023-09-14 12:09 ` Xi Ruoyao
2023-09-15 3:59 ` mengqinggang
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=1c315fdbb63b5f5eb5ff86c0b6989fccba9b5658.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=mengqinggang@loongson.cn \
--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).