public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96879] [11 Regresssion] ICE in native_encode_rtx, at simplify-rtx.c:6482
Date: Mon, 26 Oct 2020 16:05:03 +0000 [thread overview]
Message-ID: <bug-96879-4-mBcqxRzJbg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96879-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96879
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> I was hoping the aarch64 maintainers would have a look, because the above
> patch is just to show the problem, there are other issues lurking in that
> area as written.
I'm hoping to get to this in stage 3. (Too much stage 1 stuff to finish
off first. :-))
next prev parent reply other threads:[~2020-10-26 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 7:18 [Bug target/96879] New: " marxin at gcc dot gnu.org
2020-09-01 8:40 ` [Bug target/96879] " jakub at gcc dot gnu.org
2020-09-01 8:40 ` jakub at gcc dot gnu.org
2020-10-02 7:23 ` marxin at gcc dot gnu.org
2020-10-02 7:23 ` marxin at gcc dot gnu.org
2020-10-13 7:38 ` marxin at gcc dot gnu.org
2020-10-13 7:48 ` jakub at gcc dot gnu.org
2020-10-13 16:48 ` jakub at gcc dot gnu.org
2020-10-26 16:05 ` rsandifo at gcc dot gnu.org [this message]
2021-03-11 8:29 ` jakub at gcc dot gnu.org
2021-03-29 11:47 ` 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-96879-4-mBcqxRzJbg@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).