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/110790] [14 Regression] gcc -m32 generates invalid bit test code on gmp-6.2.1 Date: Mon, 24 Jul 2023 11:35:22 +0000 [thread overview] Message-ID: <bug-110790-4-g7zJI3MOnJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110790-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110790 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>: https://gcc.gnu.org/g:9f66753ef48f37729a88735ae1a2bf2d2558e69f commit r14-2743-g9f66753ef48f37729a88735ae1a2bf2d2558e69f Author: Roger Sayle <roger@nextmovesoftware.com> Date: Mon Jul 24 12:34:23 2023 +0100 [Committed] PR target/110787: Revert QImode offsets in {zero,sign}_extract. My recent patch to use QImode for bit offsets in ZERO_EXTRACTs and SIGN_EXTRACTs in the i386 backend shouldn't have resulted in any change behaviour, but as reported by Rainer it produces a bootstrap failure in gm2. This reverts the problematic patch whilst we investigate the underlying cause. Committed as obvious. 2023-07-23 Roger Sayle <roger@nextmovesoftware.com> gcc/ChangeLog PR target/110787 PR target/110790 Revert patch. * config/i386/i386.md (extv<mode>): Use QImode for offsets. (extzv<mode>): Likewise. (insv<mode>): Likewise. (*testqi_ext_3): Likewise. (*btr<mode>_2): Likewise. (define_split): Likewise. (*btsq_imm): Likewise. (*btrq_imm): Likewise. (*btcq_imm): Likewise. (define_peephole2 x3): Likewise. (*bt<mode>): Likewise (*bt<mode>_mask): New define_insn_and_split. (*jcc_bt<mode>): Use QImode for offsets. (*jcc_bt<mode>_1): Delete obsolete pattern. (*jcc_bt<mode>_mask): Use QImode offsets. (*jcc_bt<mode>_mask_1): Likewise. (define_split): Likewise. (*bt<mode>_setcqi): Likewise. (*bt<mode>_setncqi): Likewise. (*bt<mode>_setnc<mode>): Likewise. (*bt<mode>_setncqi_2): Likewise. (*bt<mode>_setc<mode>_mask): New define_insn_and_split. (bmi2_bzhi_<mode>3): Use QImode offsets. (*bmi2_bzhi_<mode>3): Likewise. (*bmi2_bzhi_<mode>3_1): Likewise. (*bmi2_bzhi_<mode>3_1_ccz): Likewise. (@tbm_bextri_<mode>): Likewise.
next prev parent reply other threads:[~2023-07-24 11:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 10:02 [Bug target/110790] New: " slyfox at gcc dot gnu.org 2023-07-24 10:12 ` [Bug target/110790] " slyfox at gcc dot gnu.org 2023-07-24 11:35 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-24 12:17 ` slyfox at gcc dot gnu.org 2023-07-24 13:24 ` rguenth at gcc dot gnu.org 2023-07-25 11:24 ` roger at nextmovesoftware dot com 2023-07-29 16:08 ` cvs-commit at gcc dot gnu.org 2023-07-29 17:14 ` slyfox at gcc dot gnu.org 2023-11-12 19:49 ` pinskia at gcc dot gnu.org 2023-11-12 20:15 ` ubizjak at gmail dot com
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-110790-4-g7zJI3MOnJ@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).