public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: John David Anglin <danglin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-6223] Fix c-c++-common/fhardened-[12].c test fails on hppa Date: Wed, 6 Dec 2023 15:39:24 +0000 (GMT) [thread overview] Message-ID: <20231206153924.40C103858D20@sourceware.org> (raw) https://gcc.gnu.org/g:458e7c937924bbcef80eb006af0b61420dbfc1c1 commit r14-6223-g458e7c937924bbcef80eb006af0b61420dbfc1c1 Author: John David Anglin <danglin@gcc.gnu.org> Date: Wed Dec 6 15:38:50 2023 +0000 Fix c-c++-common/fhardened-[12].c test fails on hppa The -fstack-protector and -fstack-protector-strong options are not supported on hppa since the stack grows up. 2023-12-06 John David Anglin <danglin@gcc.gnu.org> gcc/testsuite/ChangeLog: * c-c++-common/fhardened-1.c: Ignore __SSP_STRONG__ define if __hppa__ is defined. * c-c++-common/fhardened-2.c: Ignore __SSP__ define if __hppa__ is defined. Diff: --- gcc/testsuite/c-c++-common/fhardened-1.c | 2 +- gcc/testsuite/c-c++-common/fhardened-2.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/c-c++-common/fhardened-1.c b/gcc/testsuite/c-c++-common/fhardened-1.c index 7e6740655fe..23478be76b2 100644 --- a/gcc/testsuite/c-c++-common/fhardened-1.c +++ b/gcc/testsuite/c-c++-common/fhardened-1.c @@ -1,7 +1,7 @@ /* { dg-do compile { target *-*-linux* *-*-gnu* } } */ /* { dg-options "-fhardened -O" } */ -#ifndef __SSP_STRONG__ +#if !defined(__SSP_STRONG__) && !defined(__hppa__) # error "-fstack-protector-strong not enabled" #endif diff --git a/gcc/testsuite/c-c++-common/fhardened-2.c b/gcc/testsuite/c-c++-common/fhardened-2.c index 280ff96eb15..6ac66f9f6b7 100644 --- a/gcc/testsuite/c-c++-common/fhardened-2.c +++ b/gcc/testsuite/c-c++-common/fhardened-2.c @@ -4,7 +4,7 @@ #ifdef __SSP_STRONG__ # error "-fstack-protector-strong enabled when it should not be" #endif -#ifndef __SSP__ +#if !defined(__SSP__) && !defined(__hppa__) # error "-fstack-protector not enabled" #endif
reply other threads:[~2023-12-06 15:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231206153924.40C103858D20@sourceware.org \ --to=danglin@gcc.gnu.org \ --cc=gcc-cvs@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).