public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at mengyan1223 dot wang" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102024] [12 Regression] zero width bitfields and ABIs
Date: Thu, 31 Mar 2022 15:08:40 +0000 [thread overview]
Message-ID: <bug-102024-4-J7L4WUOBTL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102024-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102024
--- Comment #33 from Xi Ruoyao <xry111 at mengyan1223 dot wang> ---
(In reply to Segher Boessenkool from comment #31)
> Well, what do other compilers do? It's not such a good idea to break ABI
> compatibility with the 1990's compilers ;-)
Does someone have access to a Greenhills compiler here?
(In reply to Jakub Jelinek from comment #32)
> I think best would be to ignore them altogether, especially if other
> compilers do that too.
I agree the behavior of clang (or previous G++) is more "rational". To make
things more "interesting":
> So in struct B { int : 0; double a, b; }; it will go into GPR and FPR
GCC trunk puts "a" into FPR, not GPR! So the "leading" zero-width bit-fields
are ignored (GCC does not think it's a part of any "64-bit chunk"), but other
zero-width bit-fields are accounted... This is just puzzling to me.
I'll make a patch to match the behavior of clang.
next prev parent reply other threads:[~2022-03-31 15:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:36 [Bug target/102024] New: " jakub at gcc dot gnu.org
2021-08-23 14:38 ` [Bug target/102024] [12 Regression] " jakub at gcc dot gnu.org
2021-08-23 14:40 ` jakub at gcc dot gnu.org
2021-08-23 15:20 ` jakub at gcc dot gnu.org
2021-08-23 15:37 ` jakub at gcc dot gnu.org
2021-08-23 16:17 ` rsandifo at gcc dot gnu.org
2021-08-23 20:42 ` segher at gcc dot gnu.org
2021-08-23 20:49 ` segher at gcc dot gnu.org
2021-08-24 7:06 ` rguenth at gcc dot gnu.org
2021-08-24 14:13 ` matz at gcc dot gnu.org
2021-08-24 21:36 ` segher at gcc dot gnu.org
2021-08-25 19:23 ` wschmidt at gcc dot gnu.org
2021-08-25 19:33 ` wschmidt at gcc dot gnu.org
2021-08-25 20:08 ` wschmidt at gcc dot gnu.org
2021-09-03 7:53 ` cvs-commit at gcc dot gnu.org
2021-09-03 8:12 ` jakub at gcc dot gnu.org
2021-09-21 16:16 ` wschmidt at gcc dot gnu.org
2021-09-23 12:40 ` cvs-commit at gcc dot gnu.org
2022-01-10 16:47 ` cvs-commit at gcc dot gnu.org
2022-03-24 9:39 ` ebotcazou at gcc dot gnu.org
2022-03-24 11:25 ` cvs-commit at gcc dot gnu.org
2022-03-29 16:44 ` cvs-commit at gcc dot gnu.org
2022-03-29 16:45 ` cvs-commit at gcc dot gnu.org
2022-03-30 10:27 ` jakub at gcc dot gnu.org
2022-03-30 10:39 ` jakub at gcc dot gnu.org
2022-03-30 12:40 ` hp at gcc dot gnu.org
2022-03-30 12:43 ` jakub at gcc dot gnu.org
2022-03-30 13:05 ` jakub at gcc dot gnu.org
2022-03-30 13:42 ` xry111 at mengyan1223 dot wang
2022-03-30 13:53 ` jakub at gcc dot gnu.org
2022-03-30 14:34 ` xry111 at mengyan1223 dot wang
2022-03-30 19:02 ` xry111 at mengyan1223 dot wang
2022-03-31 12:36 ` segher at gcc dot gnu.org
2022-03-31 12:50 ` jakub at gcc dot gnu.org
2022-03-31 15:08 ` xry111 at mengyan1223 dot wang [this message]
2022-03-31 15:14 ` xry111 at mengyan1223 dot wang
2022-04-01 9:50 ` cvs-commit at gcc dot gnu.org
2022-04-01 14:39 ` cvs-commit at gcc dot gnu.org
2022-04-01 14:39 ` cvs-commit at gcc dot gnu.org
2022-04-02 0:47 ` segher at gcc dot gnu.org
2022-04-27 7:23 ` cvs-commit 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-102024-4-J7L4WUOBTL@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).