From: Segher Boessenkool <segher@koffie.nl>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: long long bit-fields
Date: Tue, 01 Apr 2003 00:11:00 -0000 [thread overview]
Message-ID: <3E88D929.70900@koffie.nl> (raw)
In-Reply-To: <87wuig2gcr.fsf@student.uni-tuebingen.de>
Falk Hueffner wrote:
> How about:
>
> struct { unsigned long long ull31a: 33; } x = { -1 };
> printf("%016llx\n", (x.ull31a << 48) >> 48);
>
> We don't currently promote to signed long long if it fits. Should we?
Yes. But IMHO, of course.
Segher
prev parent reply other threads:[~2003-04-01 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 19:14 Falk Hueffner
2003-03-31 8:46 ` Segher Boessenkool
2003-03-31 9:22 ` Falk Hueffner
2003-04-01 0:11 ` Segher Boessenkool [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=3E88D929.70900@koffie.nl \
--to=segher@koffie.nl \
--cc=falk.hueffner@student.uni-tuebingen.de \
--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).