public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/70150] Additonal test failures with --enable-default-pie
Date: Tue, 07 Mar 2023 07:38:01 +0000 [thread overview]
Message-ID: <bug-70150-4-BgYd7jObU8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-70150-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70150
--- Comment #28 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:
https://gcc.gnu.org/g:7e8a3dbbb26f66ce8ea60be48962022b5fb2ef55
commit r13-6518-g7e8a3dbbb26f66ce8ea60be48962022b5fb2ef55
Author: Xi Ruoyao <xry111@xry111.site>
Date: Sat Sep 24 14:45:17 2022 +0800
aarch64: testsuite: disable PIE for fuse_adrp_add_1.c [PR70150]
In PIE, symbol "fixed_regs" is addressed via GOT. It will break the
scan-assembler pattern and cause test failure with --enable-default-pie.
gcc/testsuite/ChangeLog:
PR testsuite/70150
* gcc.target/aarch64/fuse_adrp_add_1.c (dg-options): Add
-fno-pie.
next prev parent reply other threads:[~2023-03-07 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-70150-4@http.gcc.gnu.org/bugzilla/>
2022-01-25 13:54 ` allan at archlinux dot org
2023-03-07 7:37 ` cvs-commit at gcc dot gnu.org
2023-03-07 7:37 ` cvs-commit at gcc dot gnu.org
2023-03-07 7:38 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-07 7:40 ` xry111 at gcc dot gnu.org
2023-06-12 8:53 ` dkm at gcc dot gnu.org
2023-06-15 7:48 ` xry111 at gcc dot gnu.org
2023-06-15 10:17 ` rsandifo at gcc dot gnu.org
2023-06-15 10:26 ` cvs-commit at gcc dot gnu.org
2023-06-15 10:26 ` cvs-commit at gcc dot gnu.org
2023-06-15 10:26 ` cvs-commit at gcc dot gnu.org
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=bug-70150-4-BgYd7jObU8@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).