public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100041] ICE in curr_insn_transform, at lra-constraints.c:4022
Date: Mon, 12 Apr 2021 12:22:05 +0000 [thread overview]
Message-ID: <bug-100041-4-6RVqQcLtrg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100041
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|11.0 |12.0
--- Comment #20 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #19)
> I'm worried that there isn't enough time to find out before GCC11 release if
> some packages in the wild aren't using that option.
> E.g. I wonder where it comes from in this PR. Clearly it doesn't come from
> gcc, so does it come from LLVM makefiles or has the reporter just added it?
OK, let's wait with the patch after the branch, and leave things as they are
for now.
BTW: I don't think the fix for PR79514 is enough to handle any non-trivial
usage of -m96bit-long-double, and this PR reflects the fact.
next prev parent reply other threads:[~2021-04-12 12:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 3:39 [Bug c++/100041] New: " mss at tutanota dot de
2021-04-12 6:17 ` [Bug target/100041] " pinskia at gcc dot gnu.org
2021-04-12 7:30 ` mss at tutanota dot de
2021-04-12 7:32 ` mss at tutanota dot de
2021-04-12 7:34 ` marxin at gcc dot gnu.org
2021-04-12 7:39 ` mss at tutanota dot de
2021-04-12 7:40 ` marxin at gcc dot gnu.org
2021-04-12 8:52 ` mss at tutanota dot de
2021-04-12 8:54 ` mss at tutanota dot de
2021-04-12 8:55 ` mss at tutanota dot de
2021-04-12 9:08 ` mss at tutanota dot de
2021-04-12 9:09 ` rguenth at gcc dot gnu.org
2021-04-12 9:11 ` rguenth at gcc dot gnu.org
2021-04-12 9:31 ` ubizjak at gmail dot com
2021-04-12 11:08 ` marxin at gcc dot gnu.org
2021-04-12 11:21 ` ubizjak at gmail dot com
2021-04-12 11:57 ` ubizjak at gmail dot com
2021-04-12 11:59 ` ubizjak at gmail dot com
2021-04-12 12:04 ` jakub at gcc dot gnu.org
2021-04-12 12:11 ` ubizjak at gmail dot com
2021-04-12 12:14 ` jakub at gcc dot gnu.org
2021-04-12 12:22 ` ubizjak at gmail dot com [this message]
2021-04-12 12:26 ` mss at tutanota dot de
2021-04-23 16:46 ` cvs-commit at gcc dot gnu.org
2021-04-24 8:03 ` ubizjak at gmail dot com
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-100041-4-6RVqQcLtrg@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).