public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97715] [11 Regression] ICE in insn_default_length, at config/i386/i386.md:15325 since r11-4578-gd10f3e900b0377b4
Date: Wed, 04 Nov 2020 15:21:03 +0000 [thread overview]
Message-ID: <bug-97715-4-3MjQSbWeEr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97715-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97715
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|hjl at gcc dot gnu.org |hjl.tools at gmail dot com
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to qinzhao from comment #1)
> for -fzero-call-used-regs=all, when zeroing st/mm registers under x87 exit
> mode, However, command line option force no 80387 mode, the following insn
> generated to zero st registers is not recognized:
>
> (insn 27 67 28 2 (set (reg:XF 8 st)
> (const_double:XF 0.0 [0x0.0p+0])) "zero-scratch-regs-10.c":8:1 -1
> (nil))
You should avoid zeroing fixed registers.
next prev parent reply other threads:[~2020-11-04 15:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 14:11 [Bug target/97715] New: " marxin at gcc dot gnu.org
2020-11-04 14:11 ` [Bug target/97715] " marxin at gcc dot gnu.org
2020-11-04 15:19 ` qinzhao at gcc dot gnu.org
2020-11-04 15:21 ` hjl.tools at gmail dot com [this message]
2020-11-04 15:32 ` jakub at gcc dot gnu.org
2020-11-04 15:35 ` jakub at gcc dot gnu.org
2020-11-04 15:41 ` qinzhao at gcc dot gnu.org
2020-11-04 15:44 ` qinzhao at gcc dot gnu.org
2020-11-04 15:45 ` ubizjak at gmail dot com
2020-11-04 15:50 ` jakub at gcc dot gnu.org
2020-11-04 15:55 ` ubizjak at gmail dot com
2020-11-04 15:59 ` qing.zhao at oracle dot com
2020-11-04 16:04 ` jakub at gcc dot gnu.org
2020-11-04 16:08 ` ubizjak at gmail dot com
2020-11-04 16:09 ` qing.zhao at oracle dot com
2020-11-04 16:10 ` ubizjak at gmail dot com
2020-11-04 16:15 ` jakub at gcc dot gnu.org
2020-11-04 16:16 ` ubizjak at gmail dot com
2020-11-04 16:23 ` qing.zhao at oracle dot com
2020-11-04 17:48 ` jakub at gcc dot gnu.org
2020-11-04 18:09 ` jakub at gcc dot gnu.org
2020-11-04 18:39 ` qing.zhao at oracle dot com
2020-11-04 18:42 ` qing.zhao at oracle dot com
2020-11-04 20:07 ` qinzhao at gcc dot gnu.org
2020-11-05 8:56 ` marxin at gcc dot gnu.org
2020-11-05 14:58 ` cvs-commit at gcc dot gnu.org
2020-11-05 14:59 ` qinzhao 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-97715-4-3MjQSbWeEr@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).