From: Jeff Law <jeffreyalaw@gmail.com>
To: Allan McRae <allan@archlinux.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite/70230 - fix failures with default SSP
Date: Fri, 28 Jan 2022 10:45:59 -0700 [thread overview]
Message-ID: <9464aee5-eca9-47af-de9b-051ce4159284@gmail.com> (raw)
In-Reply-To: <20220127014220.3713845-1-allan@archlinux.org>
On 1/26/2022 6:42 PM, Allan McRae via Gcc-patches wrote:
> Configuring with --enable-default-ssp triggers various testsuite
> failures. These contain asm statements that are not compatible with
> -fstack-protector. Adding -fno-stack-protector to dg-options to
> work around this issue.
>
> Tested on x86_64-linux.
>
> 2022-01-26 Allan McRae <allan@archlinux.org>
>
> PR testsuite/70230
> * gcc.dg/asan/use-after-scope-4.c (dg-options): Add
> -fno-stack-protector.
> * gcc.dg/stack-usage-1.c: Likewise
> * gcc.dg/superblock.c: Likewise
> * gcc.target/i386/avx-vzeroupper-17.c: Likewise
> * gcc.target/i386/cleanup-1.c: Likewise
> * gcc.target/i386/cleanup-2.c: Likewise
> * gcc.target/i386/interrupt-redzone-1.c: Likewise
> * gcc.target/i386/interrupt-redzone-2.c: Likewise
> * gcc.target/i386/pr79793-1.c: Likewise
> * gcc.target/i386/pr79793-2.c: Likewise
> * gcc.target/i386/shrink_wrap_1.c: Likewise
> * gcc.target/i386/stack-check-11.c: Likewise
> * gcc.target/i386/stack-check-18.c: Likewise
> * gcc.target/i386/stack-check-19.c: Likewise
> * gcc.target/i386/stackalign/pr88483-1.c: Likewise
> * gcc.target/i386/stackalign/pr88483-2.c: Likewise
> * gcc.target/i386/sw-1.c: Likewise
We're actually in stage4, which means regression fixes only. But since
this only modifies the testsuite, it can't change code generation or the
like. I'll go out on a limb, ack and commit.
Jeff
prev parent reply other threads:[~2022-01-28 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 1:42 Allan McRae
2022-01-28 17:45 ` Jeff Law [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=9464aee5-eca9-47af-de9b-051ce4159284@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=allan@archlinux.org \
--cc=gcc-patches@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).