From: Jeff Law <jeffreyalaw@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>, Jeff Law <jlaw@ventanamicro.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: RFC -- targets with unsigned bifields
Date: Mon, 18 Dec 2023 11:36:13 -0700 [thread overview]
Message-ID: <2d0b6a71-33f5-4331-b160-b4f39db3ab24@gmail.com> (raw)
In-Reply-To: <fd77631d-e032-7a7e-f121-963be5bda4f@codesourcery.com>
On 12/18/23 11:32, Joseph Myers wrote:
> On Sat, 16 Dec 2023, Jeff Law wrote:
>
>> I tracked this down to the port unconditionally adding -funsigned-bitfields to
>> CC1_SPEC. According to the comment it's how the ABI is defined for the mcore
>> targets.
>
> We explicitly document (under Non-bugs in trouble.texi) that we don't do
> this, and -funsigned-bitfields is also incompatible with C++14 and later.
> So stopping adding -funsigned-bitfields like that, and telling users of
> this port to pass that option explicitly if they want its effects in
> future, would seem the obvious thing to do.
I'm not even sure there's any more users for this port. So this may be
the best solution in the end. Change, document and forget :-)
Any objections to make that change in gcc-14? It's a one-liner.
jeff
prev parent reply other threads:[~2023-12-18 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 3:29 Jeff Law
2023-12-17 8:36 ` Richard Biener
2023-12-18 18:32 ` Joseph Myers
2023-12-18 18:36 ` Jeff Law [this message]
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=2d0b6a71-33f5-4331-b160-b4f39db3ab24@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=joseph@codesourcery.com \
/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).