public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104400] [12 Regression] v850e lra/reload failure after recent change
Date: Thu, 10 Feb 2022 15:22:49 +0000 [thread overview]
Message-ID: <bug-104400-4-bPIfnzelfw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104400-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104400
--- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #2)
> NP on the timing. My biggest concern (as always) is whether or not this is
> a generic issue or a bug in the v850 target files. The former is obviously
> much more important.
>
> If it starts to look like a target issue, then feel free to punt it to me.
> While I don't know the v850 fp bits, I have retained a fair amount of
> generic v850 knowledge over the decades :-)
It is my patch pitfall for very unusual v850 insn constraint 'e!r' where e is
even general reg and subset of r.
I have a patch to fix this and after testing it I'll commit it today or
tomorrow.
next prev parent reply other threads:[~2022-02-10 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 18:57 [Bug rtl-optimization/104400] New: " law at gcc dot gnu.org
2022-02-07 7:51 ` [Bug rtl-optimization/104400] " rguenth at gcc dot gnu.org
2022-02-09 14:47 ` vmakarov at gcc dot gnu.org
2022-02-09 17:14 ` law at gcc dot gnu.org
2022-02-10 15:22 ` vmakarov at gcc dot gnu.org [this message]
2022-02-11 15:50 ` cvs-commit at gcc dot gnu.org
2022-02-11 16:57 ` law 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-104400-4-bPIfnzelfw@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).