public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/107213] New test case c-c++-common/pointer-to-fn1.c uses unsupported option  r13-3202-g67efffec943656
Date: Tue, 18 Oct 2022 17:41:19 +0000	[thread overview]
Message-ID: <bug-107213-4-3I7c9XSJKK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107213-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107213

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:cc694f45087c892e69ebbb177203c708f00b1bc7

commit r13-3365-gcc694f45087c892e69ebbb177203c708f00b1bc7
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Oct 11 12:51:40 2022 -0400

    testsuite: Only run -fcf-protection test on i?86/x86_64 [PR107213]

    This test fails on non-i?86/x86_64 targets because on those targets
    we get

      error: '-fcf-protection=full' is not supported for this target

    so this patch limits where the test is run.

            PR testsuite/107213

    gcc/testsuite/ChangeLog:

            * c-c++-common/pointer-to-fn1.c: Only run on i?86/x86_64.

  parent reply	other threads:[~2022-10-18 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 16:39 [Bug testsuite/107213] New: " seurer at gcc dot gnu.org
2022-10-11 16:42 ` [Bug testsuite/107213] " mpolacek at gcc dot gnu.org
2022-10-18 17:41 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-18 17:42 ` mpolacek at gcc dot gnu.org

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=bug-107213-4-3I7c9XSJKK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).