From: David Rundle <davekern@ihug.co.nz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: gcc
Date: Wed, 05 Sep 2001 09:04:01 +1200 [thread overview]
Message-ID: <3B9541C1.5BEFE0BA@ihug.co.nz> (raw)
hi i need help i have a data struct that matchs some hardwear but
gcc is alignin it this meins it is out of sync whit the hardwear
like
char is 2 bytes
long double is 12 bytes
will thats what gcc thinks
so i need to tell gcc not to align the data struct
may be like
noalign struct ........
the main prob is whit long double st[8]
gcc make long double 12 bytes when it need to be 10 bytes
think you
struct _i386_fpu_st
{
long long significand;
unsigned char exponent ;
/* unsigned long test ; */
} ;
struct _i386_fpu
{
unsigned short control ;
unsigned short rev0 ;
unsigned short status ;
unsigned short rev1 ;
unsigned short tag ;
unsigned short rev2 ;
unsigned long instructionPointer ;
unsigned short instructionSelector ;
unsigned short opcode ;
unsigned long operandPointer ;
unsigned short operandSelector ;
unsigned short rev3 ;
long double st[8] ;
/* struct _i386_fpu_st st[8] ; */
unsigned long rev[400] ;
} ;
extern struct _i386_fpu * i386_fpuInit(void) ;
next reply other threads:[~2001-09-04 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 21:04 David Rundle [this message]
2001-09-04 22:08 ` gcc Kurt Garloff
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=3B9541C1.5BEFE0BA@ihug.co.nz \
--to=davekern@ihug.co.nz \
--cc=linux-kernel@vger.kernel.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