public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110772] strange code generated for bit-field access
Date: Sat, 22 Jul 2023 15:23:31 +0000	[thread overview]
Message-ID: <bug-110772-4-rp6zmpe52d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110772-4@http.gcc.gnu.org/bugzilla/>

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

Roland Illig <roland.illig at gmx dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #55598|0                           |1
        is obsolete|                            |
  Attachment #55599|0                           |1
        is obsolete|                            |

--- Comment #6 from Roland Illig <roland.illig at gmx dot de> ---
Created attachment 55611
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55611&action=edit
Precompiled source from comment 5

  parent reply	other threads:[~2023-07-22 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 23:26 [Bug c/110772] New: " roland.illig at gmx dot de
2023-07-21 23:27 ` [Bug c/110772] " roland.illig at gmx dot de
2023-07-21 23:53 ` [Bug target/110772] " pinskia at gcc dot gnu.org
2023-07-22  0:08 ` pinskia at gcc dot gnu.org
2023-07-22  0:11 ` pinskia at gcc dot gnu.org
2023-07-22 15:21 ` roland.illig at gmx dot de
2023-07-22 15:23 ` roland.illig at gmx dot de [this message]
2023-07-22 15:29 ` roland.illig at gmx dot de
2023-07-22 15:50 ` roland.illig at gmx dot de

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-110772-4-rp6zmpe52d@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).