public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104458] [11/12 Regression] ICE: SIGSEGV in gen_udivmodhiqi3 -> copy_rtx with -O1 -m8bit-idiv Date: Wed, 09 Feb 2022 19:19:01 +0000 [thread overview] Message-ID: <bug-104458-4-0rdUGmI2y3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104458-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104458 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:2b399dbabd48639ab4daac462c9d82c6cf3f99cc commit r12-7146-g2b399dbabd48639ab4daac462c9d82c6cf3f99cc Author: Uros Bizjak <ubizjak@gmail.com> Date: Wed Feb 9 20:18:10 2022 +0100 i386: Force inputs to a register to avoid lowpart_subreg failure [PR104458] Input operands can be in the form of: (subreg:DI (reg:V2SF 96) 0) which chokes lowpart_subreg. Force inputs to a register, which is preferable even when the input operand is from memory. 2022-02-09 Uroš Bizjak <ubizjak@gmail.com> gcc/ChangeLog: PR target/104458 * config/i386/i386-expand.cc (ix86_split_idivmod): Force operands[2] and operands[3] into a register.. gcc/testsuite/ChangeLog: PR target/104458 * gcc.target/i386/pr104458.c: New test.
next prev parent reply other threads:[~2022-02-09 19:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-09 9:38 [Bug target/104458] New: " zsojka at seznam dot cz 2022-02-09 10:05 ` [Bug target/104458] " rguenth at gcc dot gnu.org 2022-02-09 10:54 ` ubizjak at gmail dot com 2022-02-09 19:19 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-09 22:23 ` cvs-commit at gcc dot gnu.org 2022-02-09 22:43 ` cvs-commit at gcc dot gnu.org 2022-02-09 22:45 ` ubizjak at gmail dot com 2022-02-10 14:28 ` cvs-commit at gcc dot gnu.org 2022-02-10 16:34 ` cvs-commit at gcc dot gnu.org 2022-02-10 16:35 ` cvs-commit 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-104458-4-0rdUGmI2y3@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: linkBe 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).