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 middle-end/110869] [14 regression] ICE in decompose, at rtl.h:2297
Date: Tue, 08 Aug 2023 06:54:47 +0000	[thread overview]
Message-ID: <bug-110869-4-s3icj1Iss7@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 #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stefan Schulze Frielinghaus
<stefansf@gcc.gnu.org>:

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

commit r14-3074-gf3a8dde08b420dbe9cacbc1a1febaaf77357f4d4
Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Date:   Tue Aug 8 08:53:12 2023 +0200

    rtl-optimization/110869 Fix tests cmp-mem-const-*.c for sparc

    This fixes the rather new tests cmp-mem-const-{1,2,3,4,5,6}.c for sparc.
    For -1 and -2 we need at least optimization level 2 on sparc.  For the
    sake of homogeneity, change all test cases to -O2.  For -3 and -4 we do
    not end up with a comparison of memory and a constant, and finally for
    -5 and -6 the constants are reduced by a prior optimization which means
    there is nothing left to do.  Thus excluding sparc from those tests.

    gcc/testsuite/ChangeLog:

            PR rtl-optimization/110869
            * gcc.dg/cmp-mem-const-1.c: Use optimization level 2.
            * gcc.dg/cmp-mem-const-2.c: Dito.
            * gcc.dg/cmp-mem-const-3.c: Exclude sparc from this test.
            * gcc.dg/cmp-mem-const-4.c: Dito.
            * gcc.dg/cmp-mem-const-5.c: Dito.
            * gcc.dg/cmp-mem-const-6.c: Dito.

  parent reply	other threads:[~2023-08-08  6:54 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
2023-08-07 13:41 ` stefansf at linux dot ibm.com
2023-08-08  6:54 ` cvs-commit at gcc dot gnu.org [this message]
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-s3icj1Iss7@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).