public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111743] shifts in bit field accesses don't combine with other shifts Date: Tue, 10 Oct 2023 00:32:28 +0000 [thread overview] Message-ID: <bug-111743-4-xXZPUTDZYJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111743-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111743 --- Comment #5 from Andi Kleen <andi-gcc at firstfloor dot org> --- config/i386/i386.h:#define SLOW_BYTE_ACCESS 0 You mean it doesn't define it?
next prev parent reply other threads:[~2023-10-10 0:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-09 18:57 [Bug middle-end/111743] New: " andi-gcc at firstfloor dot org 2023-10-09 19:09 ` [Bug middle-end/111743] " pinskia at gcc dot gnu.org 2023-10-09 19:19 ` andi-gcc at firstfloor dot org 2023-10-09 20:40 ` pinskia at gcc dot gnu.org 2023-10-09 20:46 ` pinskia at gcc dot gnu.org 2023-10-10 0:32 ` andi-gcc at firstfloor dot org [this message] 2023-10-10 0:40 ` pinskia 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-111743-4-xXZPUTDZYJ@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).