public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104198] [12 regression] ifcvf change breaks 64-bit SPARC bootstrap
Date: Mon, 24 Jan 2022 16:54:55 +0000	[thread overview]
Message-ID: <bug-104198-4-Ud7fn1VrtK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104198-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from rdapp at linux dot ibm.com ---
One of the s390-"specific" execution testcases fails on SPARC using the wrong
order of operands.  I'm pretty sure this is the problem.  Going to investigate
further.
Seeing this, it might make sense to make the testcases target independent if
the testsuite was indeed clean after the ifcvt patches.

  parent reply	other threads:[~2022-01-24 16:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24  8:36 [Bug rtl-optimization/104198] New: " ro at gcc dot gnu.org
2022-01-24  8:36 ` [Bug rtl-optimization/104198] " ro at gcc dot gnu.org
2022-01-24  8:43 ` pinskia at gcc dot gnu.org
2022-01-24  8:44 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-24  9:04 ` ebotcazou at gcc dot gnu.org
2022-01-24  9:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-24  9:08 ` ebotcazou at gcc dot gnu.org
2022-01-24  9:18 ` rdapp at linux dot ibm.com
2022-01-24  9:23 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-24  9:26 ` rguenth at gcc dot gnu.org
2022-01-24 16:54 ` rdapp at linux dot ibm.com [this message]
2022-01-25 12:27 ` rdapp at linux dot ibm.com
2022-01-26 17:08 ` rdapp at linux dot ibm.com
2022-01-27  9:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-27 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-31  7:14 ` [Bug rtl-optimization/104198] [12 regression] ifcvt " rdapp at linux dot ibm.com
2022-01-31 10:13 ` rdapp at linux dot ibm.com
2022-02-01  9:32 ` rdapp at linux dot ibm.com
2022-02-08 19:49 ` cvs-commit at gcc dot gnu.org
2022-03-07 15:45 ` jakub at gcc dot gnu.org
2022-03-08 11:31 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-08 11:33 ` jakub 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-104198-4-Ud7fn1VrtK@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).