From: "David A. Greene" <greened@eecs.umich.edu>
To: egcs@egcs.cygnus.com
Subject: egcs and bitfields
Date: Thu, 11 Mar 1999 14:33:00 -0000 [thread overview]
Message-ID: <36E844B2.8DAEFAAF@eecs.umich.edu> (raw)
I sent this question to the list a few days ago but got
no response. Can someone please help me out?
I'm trying to figure out the alignment rules that egcs
uses for bitfields under Linux 2.0.x. It seems that egcs
does not follow the System V ABI stardard. Specifically,
the part about not allowing bitfields to cross the
alignment boundaries of their base types (i.e. int c:17
should not cross a 32-bit boundary, but egcs allows it).
Also, bitfields declared "int" are treated as signed by
egcs while the System V ABI indicates they are unsigned.
What ABI is egcs conforming to? I need some detailed
information as we need to interface to code compiled by
egcs.
Thanks!
-Dave
WARNING: multiple messages have this Message-ID
From: "David A. Greene" <greened@eecs.umich.edu>
To: egcs@egcs.cygnus.com
Subject: egcs and bitfields
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <36E844B2.8DAEFAAF@eecs.umich.edu> (raw)
Message-ID: <19990331234600.csdokpT0fYHMsx0vIzttuHb8hH5LFm3ouJ6TBFzTQ4k@z> (raw)
I sent this question to the list a few days ago but got
no response. Can someone please help me out?
I'm trying to figure out the alignment rules that egcs
uses for bitfields under Linux 2.0.x. It seems that egcs
does not follow the System V ABI stardard. Specifically,
the part about not allowing bitfields to cross the
alignment boundaries of their base types (i.e. int c:17
should not cross a 32-bit boundary, but egcs allows it).
Also, bitfields declared "int" are treated as signed by
egcs while the System V ABI indicates they are unsigned.
What ABI is egcs conforming to? I need some detailed
information as we need to interface to code compiled by
egcs.
Thanks!
-Dave
next reply other threads:[~1999-03-11 14:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-11 14:33 David A. Greene [this message]
[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
[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=36E844B2.8DAEFAAF@eecs.umich.edu \
--to=greened@eecs.umich.edu \
--cc=egcs@egcs.cygnus.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).