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] Incorrect code generated for shifted bit field Date: Fri, 05 May 2023 18:13:01 +0000 [thread overview] Message-ID: <bug-109750-4-cfReTCPUiM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109750-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750 --- Comment #5 from jim.gray at atos dot net --- I don't know if it makes any difference, but I ran with an older version of the Intel C++ compiler on Linux, with the results below: Good output when compiling with the Intel C++ compiler on CentOS Linux release 7.7.1908 [builder@7f936516e827 ~]$ icc --version icc (ICC) 17.0.2 20170213 Copyright (C) 1985-2017 Intel Corporation. All rights reserved. [builder@af80ebc5f176 gccbug]$ icc gccbug.cpp [builder@af80ebc5f176 gccbug]$ [builder@af80ebc5f176 gccbug]$ ls -l total 28 -rwxrwxr-x 1 builder builder 22592 May 5 18:02 a.out -rw-rw-r-- 1 builder builder 3553 May 5 18:02 gccbug.cpp [builder@af80ebc5f176 gccbug]$ [builder@af80ebc5f176 gccbug]$ ./a.out Example showing GCC bug: Source = 000000020000 Target = 000000000200 Target = 020000000200 Example showing workaround for bug: Source = 000000020000 Target = 000000000200 Temp = 000000020000 Temp = 020000000000 Target = 020000000200 [builder@af80ebc5f176 gccbug]$
next prev parent reply other threads:[~2023-05-05 18:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-05 17:27 [Bug c++/109750] New: " jim.gray at atos dot net 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 [this message] 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-cfReTCPUiM@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).