public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107601] New: Change SLOW_BYTE_ACCESS  into WIDEN_MODE_ACCESS_BITFIELD target hook
Date: Thu, 10 Nov 2022 01:04:42 +0000	[thread overview]
Message-ID: <bug-107601-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107601

            Bug ID: 107601
           Summary: Change SLOW_BYTE_ACCESS  into
                    WIDEN_MODE_ACCESS_BITFIELD target hook
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: internal-improvement, missed-optimization
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

This comes up every few years even. The name SLOW_BYTE_ACCESS and documentation
is confusing even and does not describe what it does.
I found that HJL proposed a decent naming target macro back in 2006 which I
will be using as a basis going forward.

HJL's patch
https://gcc.gnu.org/legacy-ml/gcc-patches/2006-09/msg00555.html

Wilco Dijkstra's patch which just removes SLOW_BYTE_ACCESS 
https://gcc.gnu.org/legacy-ml/gcc-patches/2017-11/msg01547.html

This is part of my bit-field lowering work too.

             reply	other threads:[~2022-11-10  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  1:04 pinskia at gcc dot gnu.org [this message]
2022-11-10  1:04 ` [Bug middle-end/107601] " pinskia at gcc dot gnu.org
2022-11-10  1:36 ` pinskia at gcc dot gnu.org
2022-11-10  7:37 ` rguenth at gcc dot gnu.org
2022-11-10 22:36 ` 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-107601-4@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).