public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99905] [8/9/10/11 Regression] wrong code with -mno-mmx -mno-sse since r7-4540-gb229ab2a712ccd44 Date: Wed, 07 Apr 2021 09:39:46 +0000 [thread overview] Message-ID: <bug-99905-4-l9Iyp6JoQk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99905 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The bug seems to be on extract_compound_operation called on (zero_extract:DI (mem/c:TI (reg/f:DI 16 argp) [3 i+0 S16 A128]) (const_int 16 [0x10]) (const_int 63 [0x3f])) We have: else if (unsignedp && len < HOST_BITS_PER_WIDE_INT) tem = simplify_and_const_int (NULL_RTX, mode, simplify_shift_const (NULL_RTX, LSHIFTRT, mode, XEXP (x, 0), pos), (HOST_WIDE_INT_1U << len) - 1); but that calls simplify_shift_const with DImode and TImode MEM. I think the shift needs to be done in inner_mode and the result then converted to mode.
next prev parent reply other threads:[~2021-04-07 9:39 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-04 8:21 [Bug target/99905] New: wrong code with -mgeneral-regs-only zsojka at seznam dot cz 2021-04-06 6:24 ` [Bug target/99905] " marxin at gcc dot gnu.org 2021-04-06 6:51 ` zsojka at seznam dot cz 2021-04-06 6:53 ` [Bug target/99905] [8/9/10/11 Regression] wrong code with -mno-mmx -mno-sse zsojka at seznam dot cz 2021-04-06 7:07 ` [Bug target/99905] [8/9/10/11 Regression] wrong code with -mno-mmx -mno-sse since r7-4540-gb229ab2a712ccd44 marxin at gcc dot gnu.org 2021-04-06 8:00 ` rguenth at gcc dot gnu.org 2021-04-06 17:25 ` jakub at gcc dot gnu.org 2021-04-07 8:48 ` jakub at gcc dot gnu.org 2021-04-07 9:39 ` jakub at gcc dot gnu.org [this message] 2021-04-07 9:54 ` [Bug rtl-optimization/99905] " jakub at gcc dot gnu.org 2021-04-12 23:02 ` cvs-commit at gcc dot gnu.org 2021-04-12 23:03 ` [Bug rtl-optimization/99905] [8/9/10 " jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:52 ` [Bug rtl-optimization/99905] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` jakub 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-99905-4-l9Iyp6JoQk@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).