From: Joseph Myers <joseph@codesourcery.com>
To: 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 18:32:20 +0000 [thread overview]
Message-ID: <fd77631d-e032-7a7e-f121-963be5bda4f@codesourcery.com> (raw)
In-Reply-To: <7a5ec7af-fdbf-470f-9414-bf4110331d0a@ventanamicro.com>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-12-18 18:32 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 [this message]
2023-12-18 18:36 ` Jeff Law
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=fd77631d-e032-7a7e-f121-963be5bda4f@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.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).