From: Ribamar Santarosa de Sousa <ribamar.sousa@ic.unicamp.br>
To: Richard Cooper <generic@xersedefixion.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: newbie question about integers size/portabilty.
Date: Tue, 28 Dec 2004 13:20:04 -0200 [thread overview]
Message-ID: <20041228152004.GB7304@ic.unicamp.br> (raw)
In-Reply-To: <opsjpz0szcuqea3r@sucks.airplane.fire>
> > Does anyone know where i can get a accurate table for gcc compiler?
>
> I think that char is 8, short is 16, long is 32, and int I think is also
> 32. I'm pretty sure. That's the values I use when I have to convert
> those stupid size names in C structures into something that actually
> exists, and it seems to always work.
>
> > i am mixing several integer types to pass to a hardware data structure,
> > this is not enough, i need exact values.
>
> Oh, well, then, if you're doing something hardware specific, I suppose you
> can say to heck with the portability aspect. So just use char for 8,
> short for 16, and int for 32 and be done with it.
Thanks for the funny approach... Now i'm convinced that the above values
for integers must work... Just to let you know i can't say to heck the
portability aspect because i am porting the module, so the hell is where
I am :)
Contented, Riba.
next prev parent reply other threads:[~2004-12-28 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 12:29 newbie question about integers size/portabilty Ribamar Santarosa de Sousa
2004-12-28 13:35 ` Richard Cooper
2004-12-28 15:20 ` Ribamar Santarosa de Sousa [this message]
2004-12-30 9:10 ` Frederic Marmond
2004-12-28 22:38 ` Brian Raiter
2004-12-28 23:52 ` Ribamar Santarosa de Sousa
2004-12-29 0:17 ` Brian Raiter
2004-12-29 1:05 ` Ribamar Santarosa de Sousa
2004-12-29 1:31 ` Herbert Poetzl
2004-12-29 7:21 ` OT: " Richard Cooper
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=20041228152004.GB7304@ic.unicamp.br \
--to=ribamar.sousa@ic.unicamp.br \
--cc=generic@xersedefixion.com \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).