public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Eric Botcazou <botcazou@adacore.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR target/90458
Date: Sat, 11 Mar 2023 19:35:53 -0500	[thread overview]
Message-ID: <CAF1jjLua0mjKBVZFONz9g86pSvsvmkeACi=03BZzXzarBeOrGw@mail.gmail.com> (raw)
In-Reply-To: <9eab1040-d6ee-1dd5-e22a-d8991e1550bd@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

The reason would be to show that they continue to not ICE as they used to.
No go paths are just as useful as go paths.

On Sat, Mar 11, 2023, 10:57 Jeff Law <jeffreyalaw@gmail.com> wrote:

>
>
> 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
>

      reply	other threads:[~2023-03-12  0:36 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
2023-03-12  0:35       ` NightStrike [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='CAF1jjLua0mjKBVZFONz9g86pSvsvmkeACi=03BZzXzarBeOrGw@mail.gmail.com' \
    --to=nightstrike@gmail.com \
    --cc=botcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@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).