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 target/100305] [10 Regression] aarch64: ICE in output_operand_lossage with -O3
Date: Thu, 29 Apr 2021 09:45:39 +0000 [thread overview]
Message-ID: <bug-100305-4-fzFj0mRzf9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100305-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100305
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:a515ce926b9d779922debc33ecad424c9ac22c65
commit r11-8327-ga515ce926b9d779922debc33ecad424c9ac22c65
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Apr 29 11:42:08 2021 +0200
testsuite: Remove dg-options from pr100305.c [PR100305]
The test FAILs on i?86-linux (due to -Wpsabi warnings). But, on closer
inspection it seems there is another problem, the dg-options in the
testcase
means that the test is compiled with -O0 -O, -O1 -O, -O2 -O, -O3 -O, -Os -O
etc. options, so effectively is tested multiple times with the same
options.
Fixed by dropping the dg-options line, then we have -w by default and
iterate
over all the optimization levels (including the -O).
2021-04-29 Jakub Jelinek <jakub@redhat.com>
PR target/100305
* gcc.c-torture/compile/pr100305.c: Remove dg-options. Add PR
line.
(cherry picked from commit 62a44a9797edce11b1f7051ea0016ee975d41233)
next prev parent reply other threads:[~2021-04-29 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 6:13 [Bug c++/100305] New: ICE in output_operand_lossage with -march=armv8.2-a -O3 gilles.gouaillardet at gmail dot com
2021-04-28 6:25 ` [Bug c++/100305] " acoplan at gcc dot gnu.org
2021-04-28 6:26 ` acoplan at gcc dot gnu.org
2021-04-28 6:27 ` acoplan at gcc dot gnu.org
2021-04-28 7:47 ` [Bug target/100305] [11/12 Regression] aarch64: ICE in output_operand_lossage with -O3 gilles.gouaillardet at gmail dot com
2021-04-28 7:50 ` pinskia at gcc dot gnu.org
2021-04-28 8:05 ` pinskia at gcc dot gnu.org
2021-04-28 9:50 ` rsandifo at gcc dot gnu.org
2021-04-28 16:55 ` cvs-commit at gcc dot gnu.org
2021-04-28 16:58 ` [Bug target/100305] [10/11/12 " rsandifo at gcc dot gnu.org
2021-04-29 8:28 ` cvs-commit at gcc dot gnu.org
2021-04-29 9:44 ` [Bug target/100305] [10 " cvs-commit at gcc dot gnu.org
2021-04-29 9:45 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-30 1:40 ` gilles.gouaillardet at gmail dot com
2021-04-30 14:18 ` rsandifo at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2021-08-17 14:14 ` cvs-commit at gcc dot gnu.org
2021-08-17 14:16 ` rsandifo 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-100305-4-fzFj0mRzf9@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).