From: Jeff Law <jeffreyalaw@gmail.com>
To: Eric Botcazou <botcazou@adacore.com>,
NightStrike <nightstrike@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR target/90458
Date: Sat, 11 Mar 2023 08:56:58 -0700 [thread overview]
Message-ID: <9eab1040-d6ee-1dd5-e22a-d8991e1550bd@gmail.com> (raw)
In-Reply-To: <5906630.lOV4Wx5bFT@fomalhaut>
On 2/16/23 01:16, Eric Botcazou via Gcc-patches wrote:
>> This fixes dg.exp/stack-check-2.c, -7, 8, and -16.c, which is great!
>
> Try the attached patch.
I'd suggest going ahead and applying the fix to
check_effective_target_supports_stack_clash_protection.
There's really not a strong reason to run those tests on a cygwin or
mingw target given how probing is done (out of line).
Jeff
next prev parent reply other threads:[~2023-03-11 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 15:24 Eric Botcazou
2023-02-15 19:05 ` Jeff Law
2023-02-16 3:27 ` NightStrike
2023-02-16 8:16 ` Eric Botcazou
2023-02-17 8:56 ` NightStrike
2023-02-17 9:18 ` Eric Botcazou
2023-02-17 19:49 ` Jeff Law
2023-03-11 15:56 ` Jeff Law [this message]
2023-03-12 0:35 ` NightStrike
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=9eab1040-d6ee-1dd5-e22a-d8991e1550bd@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@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).