From: Daniel Jacobowitz <drow@false.org>
To: gcc@gcc.gnu.org
Subject: Re: ENUM_BITFIELD and -fshort-enums
Date: Thu, 09 Dec 2004 18:00:00 -0000 [thread overview]
Message-ID: <20041209180035.GA29063@nevyn.them.org> (raw)
In-Reply-To: <20041209174614.GA28319@nevyn.them.org>
On Thu, Dec 09, 2004 at 12:46:14PM -0500, Daniel Jacobowitz wrote:
> I tried to build a native arm-unknown-linux-gnueabi compiler yesterday.
> The only major problem was the fact that EABI defaults to
> -fshort-enums. rtl.h has this:
>
> /* The kind of expression this is. */
> ENUM_BITFIELD(rtx_code) code: 16;
>
> But since there are only 164 RTL codes at present, with -fshort-enums
> the underlying type of enum rtx_code is "char". So GCC gives an error
> that the bitfield is wider than its type.
>
> For now I'm just using an x-linuxeabi file which builds GCC using
> -fno-short-enums, but that's not a good solution. Should this bitfield
> be allowed?
Other alternative fixes:
- Add an RTX code with value 65535 to force the enum to be large
enough.
- Shrink the bitfield and leave 8 bits of padding in struct rtx_def.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-09 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 17:46 Daniel Jacobowitz
2004-12-09 18:00 ` Daniel Jacobowitz [this message]
2004-12-09 18:16 ` Steven Bosscher
2004-12-15 20:58 ` Mark Mitchell
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=20041209180035.GA29063@nevyn.them.org \
--to=drow@false.org \
--cc=gcc@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).