From: Doug Semler <doug@seaspace.com>
To: Robert Lipe <robertlipe@usa.net>
Cc: "David A. Greene" <greened@eecs.umich.edu>,
"Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>,
egcs@egcs.cygnus.com
Subject: Re: egcs and bitfields
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <199903121741.JAA24401@vortex.seaspace.com> (raw)
Message-ID: <19990331234600._aqWtulvwVx8XitL0jyFLR_3jqL7oAfKptEPJBjw1fs@z> (raw)
In-Reply-To: <19990312104540.D1570@rjlhome.sco.com>
> > #include <stdio.h>
> >
> > struct foo { int c:3; } x = { 7 };
> >
> > int main(void)
> > {
> > printf("%d\n", x.c);
> >
> > return(0);
> > }
> >
> > >>-drakh-> egcc fieldinit.c
> > >>-drakh-> ./a.out
> > -1
> >
> > I think the output should be 7, since an "int"
> > bitfield is supposed
> > to be unsigned according to the i386 SysV ABI.
>
> While I can't comment on any correctness issues in the example or
> pertinence of various ABI specs, I can confirm that your example behaves
> differently on different System V/386's.
>
>
> On OpenServer:
> /bin/cc -1
> egcs 1.1.1 -1
> icc 7
> udk cc 7
>
> On UnixWare 7.0.1
> /bin/cc 7
> egcs 1.1.1 -1
>
>
> Note that /bin/cc on SVR5 is essentially the same as UDK on OSR5. Since
> /bin/cc on OpenServer had parentage in the code that became those two
> compilers, I'm guessing that it was an intentional ABI change between
> the OpenServer lineage (more iBCS2-ish) and the SVR4 lineage.
I am assuming egcs uses the ABI's definition of whether a bitfield is
signed or unsigned???? According to the standard (6.7.2) unqualified
type int is implementation defined (cf C++ 9.6)
So, does egcs use the same implementation across all platforms?
---
Doug Semler | doug@seaspace.com
SeaSpace Corporation | Garbage In -- Gospel Out
Least Senior Software Developer; | Minister of things to do Next Quarter
Low Man on the Totem Pole | (but will Never Be Done) DNRC O-
A closed mind is a terrible thing | Bus Error (passengers dumped)
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/M d---(pu) s++:- a-- C++ UILSH+++$ P--- L++ E--- W+
N++ o-- K? w--(++$) O- M-- V- PS+ !PE Y PGP t(+) 5+++ X+
R- tv+(-) b+(++) DI++++ D G e++>++++ h!>--- r% y+>+++++**
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-11 14:33 David A. Greene
[not found] ` < 36E844B2.8DAEFAAF@eecs.umich.edu >
1999-03-11 15:14 ` Martin v. Loewis
[not found] ` < 199903112300.AAA19947@mira.isdn.cs.tu-berlin.de >
1999-03-11 15:41 ` Robert Lipe
1999-03-31 23:46 ` Robert Lipe
1999-03-12 7:16 ` David A. Greene
[not found] ` < 36E92F61.5951621@eecs.umich.edu >
1999-03-12 8:48 ` Robert Lipe
[not found] ` < 19990312104540.D1570@rjlhome.sco.com >
1999-03-12 9:41 ` Doug Semler [this message]
[not found] ` < 199903121741.JAA24401@vortex.seaspace.com >
1999-03-12 9:59 ` Robert Lipe
1999-03-31 23:46 ` Robert Lipe
1999-03-12 13:26 ` Martin v. Loewis
[not found] ` < 199903122118.WAA00520@mira.isdn.cs.tu-berlin.de >
1999-03-12 13:52 ` Doug Semler
1999-03-31 23:46 ` Doug Semler
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Doug Semler
1999-03-31 23:46 ` Robert Lipe
1999-03-12 9:27 ` Martin v. Loewis
1999-03-12 10:47 ` David A. Greene
1999-03-31 23:46 ` David A. Greene
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` David A. Greene
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` David A. Greene
1999-03-12 7:20 David A. Greene
1999-03-31 23:46 ` David A. Greene
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=199903121741.JAA24401@vortex.seaspace.com \
--to=doug@seaspace.com \
--cc=egcs@egcs.cygnus.com \
--cc=greened@eecs.umich.edu \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=robertlipe@usa.net \
/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).