public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/112786] [14 Regression] gcc.dg/tree-ssa/scev-3.c scev-4.c and scev-5.c XPASSing on most ilp32 targets
Date: Sat, 02 Dec 2023 00:23:45 +0000	[thread overview]
Message-ID: <bug-112786-4-dAoIZEZCm8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112786-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Note they XPASS on the 13 branch as well IIRC.

XPASS without Alex patch?  Is that XPASS a typo for FAIL or PASS?

Either way, they FAIL, for ia32 say these results from gcc-testresults@:

i386-pc-solaris2.11
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800123.html

x86_64-pc-linux-gnu -m32 (but not -mx32 nor default)
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800107.html

i686-pc-linux-gnu
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800113.html

And PASS for these:
sparc-sun-solaris2.11
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800134.html

avr-unknown-none
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800623.html

pru-unknown-elf
https://gcc.gnu.org/pipermail/gcc-testresults/2023-November/800630.html

  parent reply	other threads:[~2023-12-02  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 17:05 [Bug testsuite/112786] New: " hp at gcc dot gnu.org
2023-11-30 17:05 ` [Bug testsuite/112786] " hp at gcc dot gnu.org
2023-12-01  3:45 ` hp at gcc dot gnu.org
2023-12-01  7:21 ` rguenth at gcc dot gnu.org
2023-12-02  0:23 ` hp at gcc dot gnu.org [this message]
2023-12-09  1:03 ` cvs-commit at gcc dot gnu.org
2023-12-09 18:07 ` hp 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-112786-4-dAoIZEZCm8@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).