public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/97680] [11 Regression] new test case c-c++-common/zero-scratch-regs-10.c in r11-4578 has excess errors
Date: Wed, 04 Nov 2020 13:26:20 +0000	[thread overview]
Message-ID: <bug-97680-4-KIY84CTwvp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97680-4@http.gcc.gnu.org/bugzilla/>

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

rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rsandifo at gcc dot gnu.org

--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Err, please dg-skip the tests for ! supported targets.  They also fail on
> x86_64 with -m32 btw.
The point is that these tests are flushing out which those targets are,
since nobody knows at present.  Most targets are supported naturally:
it's certainly not just an x86_64 or aarch64 thing.  But some targets
have special requirements that mean they would need to define a simple
hook in order to support the option.

So if this sorry() fires, we need to decide whether to add support
or live with the option being unsupported for that target combination.

  parent reply	other threads:[~2020-11-04 13:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 20:00 [Bug testsuite/97680] New: " seurer at gcc dot gnu.org
2020-11-02 20:12 ` [Bug testsuite/97680] " qinzhao at gcc dot gnu.org
2020-11-03  7:22 ` [Bug testsuite/97680] [11 Regression] " rguenth at gcc dot gnu.org
2020-11-03 14:32 ` qinzhao at gcc dot gnu.org
2020-11-04 13:26 ` rsandifo at gcc dot gnu.org [this message]
2020-11-07 16:43 ` iains at gcc dot gnu.org
2020-11-08  9:44 ` iains at gcc dot gnu.org
2021-01-14  9:32 ` rguenth at gcc dot gnu.org
2021-02-23 12:27 ` rguenth at gcc dot gnu.org
2021-02-26 12:17 ` rguenth at gcc dot gnu.org
2021-02-26 12:17 ` rguenth at gcc dot gnu.org
2021-02-26 16:18 ` qing.zhao at oracle dot com
2021-03-18 14:26 ` cvs-commit at gcc dot gnu.org
2021-03-18 16:17 ` jakub at gcc dot gnu.org
2021-03-18 17:49 ` clyon at gcc dot gnu.org
2021-03-31  6:58 ` cvs-commit at gcc dot gnu.org
2021-03-31  7:03 ` [Bug testsuite/97680] [12 " jakub at gcc dot gnu.org
2022-05-06  8:30 ` [Bug testsuite/97680] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:21 ` [Bug testsuite/97680] [12/13/14 " rguenth 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-97680-4-KIY84CTwvp@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).