public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Marek Polacek via Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v5] c-family: ICE with [[gnu::nocf_check]] [PR106937]
Date: Tue, 11 Oct 2022 16:03:12 -0400	[thread overview]
Message-ID: <Y0XMAFsK0kKKPUFV@redhat.com> (raw)
In-Reply-To: <mvmbkqig64i.fsf@suse.de>

On Tue, Oct 11, 2022 at 09:40:45AM +0200, Andreas Schwab via Gcc-patches wrote:
> On Okt 10 2022, Marek Polacek via Gcc-patches wrote:
> 
> > diff --git a/gcc/testsuite/c-c++-common/pointer-to-fn1.c b/gcc/testsuite/c-c++-common/pointer-to-fn1.c
> > new file mode 100644
> > index 00000000000..975885462e9
> > --- /dev/null
> > +++ b/gcc/testsuite/c-c++-common/pointer-to-fn1.c
> > @@ -0,0 +1,18 @@
> > +/* PR c++/106937 */
> > +/* { dg-options "-fcf-protection" } */
> 
> FAIL: c-c++-common/pointer-to-fn1.c  -Wc++-compat  (test for excess errors)
> Excess errors:
> cc1: error: '-fcf-protection=full' is not supported for this target

Thanks, patch posted.

Marek


      reply	other threads:[~2022-10-11 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 22:49 [PATCH] " Marek Polacek
2022-09-30 13:12 ` Jason Merrill
2022-10-04 23:06   ` [PATCH v2] " Marek Polacek
2022-10-06 21:42     ` Jason Merrill
2022-10-07  2:12       ` [PATCH v3] " Marek Polacek
2022-10-07 16:17         ` Jason Merrill
2022-10-07 21:08           ` [PATCH v4] " Marek Polacek
2022-10-07 21:56             ` Jason Merrill
2022-10-07 22:16               ` Marek Polacek
2022-10-10 14:49                 ` Jason Merrill
2022-10-10 19:18                   ` [PATCH v5] " Marek Polacek
2022-10-10 19:23                     ` Jason Merrill
2022-10-11  7:40                     ` Andreas Schwab
2022-10-11 20:03                       ` Marek Polacek [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=Y0XMAFsK0kKKPUFV@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=schwab@suse.de \
    /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).