public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101177] sh3: internal compiler error: Illegal instruction
Date: Wed, 07 Jul 2021 14:33:53 +0000 [thread overview]
Message-ID: <bug-101177-4-fAKLr1EoNv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101177-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101177
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Harold Gutch from comment #1)
> I cannot claim to understand the details of this patch, but note that in the
> second part of the diff the condition gets inverted.
Yes, that looks like a clear mistake. I don't know why I did that, perhaps
at first I flipped the control flow there? Who knows. Sorry for it anyway!
next prev parent reply other threads:[~2021-07-07 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 6:58 [Bug target/101177] New: " roland.illig at gmx dot de
2021-07-01 21:40 ` [Bug target/101177] " gcc_bugzilla at foobar dot franken.de
2021-07-01 21:43 ` gcc_bugzilla at foobar dot franken.de
2021-07-05 11:30 ` gcc_bugzilla at foobar dot franken.de
2021-07-07 14:33 ` segher at gcc dot gnu.org [this message]
2023-10-20 9:20 ` glaubitz at physik dot fu-berlin.de
2023-10-20 9:39 ` glaubitz at physik dot fu-berlin.de
2023-10-20 9:51 ` cvs-commit at gcc dot gnu.org
2023-10-20 9:55 ` cvs-commit at gcc dot gnu.org
2023-10-20 10:01 ` cvs-commit at gcc dot gnu.org
2023-10-20 10:05 ` cvs-commit at gcc dot gnu.org
2023-10-20 10:05 ` olegendo at gcc dot gnu.org
2023-10-20 10:14 ` glaubitz at physik dot fu-berlin.de
2023-10-20 10:17 ` olegendo 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-101177-4-fAKLr1EoNv@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).