From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>,
Jeff Law <jeffreyalaw@gmail.com>,
Richard Biener <richard.guenther@gmail.com>
Subject: Ping^4: [PATCH 0/2] Fix two test failures with --enable-default-pie [PR70150]
Date: Tue, 25 Jun 2024 20:35:09 +0800 [thread overview]
Message-ID: <1d8b5ec25a2bfc9c8f8cc57a0f9af5ee2a1e907c.camel@xry111.site> (raw)
In-Reply-To: <b164b992a50aa8e25f2d9c4d7a5c34ec7f6d6d73.camel@xry111.site>
Ping^4 https://gcc.gnu.org/pipermail/gcc-patches/2024-May/650763.html
On Mon, 2024-05-06 at 12:45 +0800, Xi Ruoyao wrote:
> In GCC 14.1-rc1, there are two new (comparing to GCC 13) failures if
> the build is configured --enable-default-pie. Let's fix them.
>
> Tested on x86_64-linux-gnu. Ok for trunk and releases/gcc-14?
>
> Xi Ruoyao (2):
> i386: testsuite: Add -no-pie for pr113689-1.c [PR70150]
> i386: testsuite: Adapt fentryname3.c for r14-811 change [PR70150]
>
> gcc/testsuite/gcc.target/i386/fentryname3.c | 3 +--
> gcc/testsuite/gcc.target/i386/pr113689-1.c | 2 +-
> 2 files changed, 2 insertions(+), 3 deletions(-)
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2024-06-25 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 4:45 Xi Ruoyao
2024-05-06 4:45 ` [PATCH 1/2] i386: testsuite: Add -no-pie for pr113689-1.c [PR70150] Xi Ruoyao
2024-05-06 4:45 ` [PATCH 2/2] i386: testsuite: Adapt fentryname3.c for r14-811 change [PR70150] Xi Ruoyao
2024-05-15 9:59 ` Ping: [PATCH 0/2] Fix two test failures with --enable-default-pie [PR70150] Xi Ruoyao
2024-05-29 6:36 ` Ping^2: " Xi Ruoyao
2024-06-09 15:24 ` Ping^3: " Xi Ruoyao
2024-06-25 12:35 ` Xi Ruoyao [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=1d8b5ec25a2bfc9c8f8cc57a0f9af5ee2a1e907c.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
/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).