From: don bailey <don.bailey@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] bitfields
Date: Wed, 6 Jun 2007 17:34:00 -0600 [thread overview]
Message-ID: <46674468.6050707@gmail.com> (raw)
In-Reply-To: <5fc4d15bc92167d17cac73461f327df3@coraid.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
erik quanstrom wrote:
> actually, if bit fields operate on 2s complement i think
> that's the correct answer.
>
> if you have a n-bit integer ~0 (all ones) is -1. so if you
> have a one-bit signed integer, the possiblities are 0b and
> 1b which should be 0 and -1.
That's my take on it as long as the type is defined as signed.
Did GNU always enforce bitfields to be unsigned before? What
was the reasoning behind this change?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGZ0RoyWX0NBMJYAcRAk1kAJsHjzP5/VlPKVfgGKaotVjx/Ema3gCfXcY2
pORPJK00rGWu4oGeBaW1mDU=
=TTAS
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-06-06 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:57 erik quanstrom
2007-06-06 23:34 ` don bailey [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=46674468.6050707@gmail.com \
--to=don.bailey@gmail.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).