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: Thu, 15 Jun 2023 10:26:48 +0000 [thread overview] Message-ID: <bug-70150-4-K4uxFv2vWg@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 #33 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>: https://gcc.gnu.org/g:e8ee5a0b00dc7a7c25dd3264e9007f440457a791 commit r12-9699-ge8ee5a0b00dc7a7c25dd3264e9007f440457a791 Author: Xi Ruoyao <xry111@xry111.site> Date: Sat Sep 24 13:57:19 2022 +0800 aarch64: testsuite: disable PIE for aapcs64 tests [PR70150] If GCC is built with --enable-default-pie, a lot of aapcs64 tests fail because relocation unsupported in PIE is used. gcc/testsuite/ChangeLog: PR testsuite/70150 * gcc.target/aarch64/aapcs64/aapcs64.exp (additional_flags): Add -fno-pie -no-pie. (cherry picked from commit f30f04b1fbd4b4e13a7535fad8e698c7b24db9b8)
next prev parent reply other threads:[~2023-06-15 10:26 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 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 [this message] 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-K4uxFv2vWg@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: linkBe 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).