public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jim.gray at atos dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109750] New: Incorrect code generated for shifted bit field
Date: Fri, 05 May 2023 17:27:48 +0000 [thread overview]
Message-ID: <bug-109750-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
Bug ID: 109750
Summary: Incorrect code generated for shifted bit field
Product: gcc
Version: 9.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jim.gray at atos dot net
Target Milestone: ---
Created attachment 55008
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55008&action=edit
Tar file with source, assembly listing, compile script, executable
Attached is a simple program that shows the problem encountered.
Bad output when compiling with GCC compiler on Ubuntu
~/gcc-bug$ ./gccbug
Source = 000000020000
Target = 000000000200
Target = 1777777777760000000200
Good output when compiling with MS C++ compiler on Windows:
>gccbug
Source = 000000020000
Target = 000000000200
Target = 020000000200
next reply other threads:[~2023-05-05 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 17:27 jim.gray at atos dot net [this message]
2023-05-05 17:33 ` [Bug c++/109750] " pinskia at gcc dot gnu.org
2023-05-05 17:37 ` pinskia at gcc dot gnu.org
2023-05-05 17:57 ` jim.gray at atos dot net
2023-05-05 18:00 ` pinskia at gcc dot gnu.org
2023-05-05 18:13 ` jim.gray at atos dot net
2023-05-05 18:21 ` pinskia at gcc dot gnu.org
2023-05-05 18:22 ` 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-109750-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).