public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110869] [14 regression] ICE in decompose, at rtl.h:2297
Date: Mon, 07 Aug 2023 12:29:43 +0000	[thread overview]
Message-ID: <bug-110869-4-f95oePJIIF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110869-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #16 from Stefan Schulze Frielinghaus <stefansf at linux dot
> ibm.com> ---
> Turns out that my dejagnu foo is weak ;-) I came up with a wrong target
> selector. Should be fixed in the new attachment.

Right: DejaGnu selector syntax is tricky indeed ;-(

Now tested on sparc-sun-solaris2.11 and amd-64-pc-solaris2.11: works as
expected.

One suggestion: in case you exclude a particular target by triple, it's
helpful to add a short comment explaining why this was done.  This way,
if the test later is discovered to FAIL on a different target, it's
easier to see if this is the same issue.  When using effective-target
keywords instead, the semantics of the exclusion is easier to
understand.

  parent reply	other threads:[~2023-08-07 12:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 16:26 [Bug middle-end/110869] New: " ro at gcc dot gnu.org
2023-08-01 16:27 ` [Bug middle-end/110869] " ro at gcc dot gnu.org
2023-08-01 18:20 ` pinskia at gcc dot gnu.org
2023-08-01 19:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-02  7:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-02  9:05 ` stefansf at linux dot ibm.com
2023-08-02  9:17 ` ro at gcc dot gnu.org
2023-08-02  9:50 ` ebotcazou at gcc dot gnu.org
2023-08-02 14:05 ` stefansf at linux dot ibm.com
2023-08-02 19:44 ` cvs-commit at gcc dot gnu.org
2023-08-04  7:53 ` ro at gcc dot gnu.org
2023-08-04  7:53 ` ro at gcc dot gnu.org
2023-08-04  8:38 ` stefansf at linux dot ibm.com
2023-08-04  8:40 ` stefansf at linux dot ibm.com
2023-08-04  8:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-04  9:42 ` stefansf at linux dot ibm.com
2023-08-04 14:16 ` stefansf at linux dot ibm.com
2023-08-04 14:18 ` stefansf at linux dot ibm.com
2023-08-07 12:29 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-08-07 13:41 ` stefansf at linux dot ibm.com
2023-08-08  6:54 ` cvs-commit at gcc dot gnu.org
2023-10-02  5:23 ` xry111 at gcc dot gnu.org
2023-10-02  5:24 ` xry111 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-110869-4-f95oePJIIF@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).