public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97701] [10/11 Regression] aarch64: ICE in extract_constrain_insn since r10-4447-g095f78c6
Date: Fri, 29 Jan 2021 20:00:45 +0000 [thread overview]
Message-ID: <bug-97701-4-58OQfmOA0M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97701-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97701
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #9)
> I've committed the patch only to the trunk. I believe the bug on the trunk
> is still present but not triggered by the test.
See #c5, by using ? 2 : 1 instead of ? 2 : 0 it should trigger it on the trunk
too.
next prev parent reply other threads:[~2021-01-29 20:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 14:41 [Bug target/97701] New: " acoplan at gcc dot gnu.org
2020-11-03 14:41 ` [Bug target/97701] " acoplan at gcc dot gnu.org
2020-11-03 15:01 ` rguenth at gcc dot gnu.org
2020-11-20 8:30 ` jakub at gcc dot gnu.org
2020-11-20 15:17 ` acoplan at gcc dot gnu.org
2020-11-20 15:54 ` acoplan at gcc dot gnu.org
2020-11-20 16:13 ` acoplan at gcc dot gnu.org
2021-01-14 9:35 ` rguenth at gcc dot gnu.org
2021-01-26 11:25 ` jakub at gcc dot gnu.org
2021-01-28 18:29 ` vmakarov at gcc dot gnu.org
2021-01-29 19:54 ` cvs-commit at gcc dot gnu.org
2021-01-29 19:55 ` vmakarov at gcc dot gnu.org
2021-01-29 20:00 ` jakub at gcc dot gnu.org [this message]
2021-01-29 20:13 ` vmakarov at gcc dot gnu.org
2021-01-29 21:06 ` cvs-commit at gcc dot gnu.org
2021-02-03 15:57 ` [Bug target/97701] [10 " jakub at gcc dot gnu.org
2021-02-04 21:04 ` cvs-commit at gcc dot gnu.org
2021-03-31 9:08 ` acoplan at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07 9:11 ` rguenth 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-97701-4-58OQfmOA0M@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).