Hi,
On Thu, Nov 27, 2014 at 10:50:26AM +, Edmund Grimley Evans wrote:
> http://wiki.debian.org/ArchitectureSpecificsMemo
>
> Some suggestions for improving this table:
>
> 1. About half of the table is taken up with sizeof information, some
> of which could be expressed mo
On Thu, Nov 27, 2014 at 10:50:26 +, Edmund Grimley Evans wrote:
> http://wiki.debian.org/ArchitectureSpecificsMemo
>
> Some suggestions for improving this table:
>
> 1. About half of the table is taken up with sizeof information, some
> of which could be expressed more c
On Thu, 27 Nov 2014, Edmund Grimley Evans wrote:
> of which could be expressed more concisely. (Are all Debian
> architectures ILP32 or LP64? Any rare exceptions could be described in
I think so. Probably even all Linux architectures?
> 4. I'd like to see some information about va_list added as
http://wiki.debian.org/ArchitectureSpecificsMemo
Some suggestions for improving this table:
1. About half of the table is taken up with sizeof information, some
of which could be expressed more concisely. (Are all Debian
architectures ILP32 or LP64? Any rare exceptions could be described in
a
* Bernd Eckenfels:
> In article <[EMAIL PROTECTED]> you wrote:
>>>sizeof(char) == 1
>
>> I just removed them for this reason.
>
> Maybe we need to specify CHAR_BITS instead?
Too much Java programming? 8-)
POSIX requires CHAR_BITS to be 8 these days.
--
To UNSUBSCRIBE, email to [EMAIL PROT
On Sat, 2008-04-26 at 20:21 +0200, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> >>sizeof(char) == 1
>
> > I just removed them for this reason.
>
> Maybe we need to specify CHAR_BITS instead?
Maybe some day Debian will run on an architecture where CHAR_BITS != 8,
but I
In article <[EMAIL PROTECTED]> you wrote:
>>sizeof(char) == 1
> I just removed them for this reason.
Maybe we need to specify CHAR_BITS instead?
Gruss
Bernd
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, 2008-04-26 at 00:15 -0400, Zack Weinberg wrote:
> I looked at the page: this seems like an appropriate moment to mention
> something that should be a lot more widely known than it is:
>
>sizeof(char) == 1
>sizeof(signed char) == 1
>sizeof(unsigned char) == 1
>
> Those three eq
On Sat, 2008-04-26 at 12:29 +0200, Florian Weimer wrote:
> * Cyril Brulebois:
>
> > I'm wondering whether the ArchitectureSpecificsMemo[1] wiki page is
> > (well-)known, and whether its content got reviewed, esp. by porters of
> > each architecture, who could fi
* Cyril Brulebois:
> I'm wondering whether the ArchitectureSpecificsMemo[1] wiki page is
> (well-)known, and whether its content got reviewed, esp. by porters of
> each architecture, who could fix obvious errors or typos, or eventually
> add special-cases, exceptions, and the
On Fri, Apr 25, 2008 at 05:06:59PM +0200, Petter Reinholdtsen wrote:
> 'arm' is said to be LE, but I believe it differ for integers and
> floating point numbers. Is 'arm' in the list the 'arm' archtecture?
> What about 'armel' and 'armeb'?
on arm (unlike armeb and armel), doubles are two little-e
I looked at the page: this seems like an appropriate moment to mention
something that should be a lot more widely known than it is:
sizeof(char) == 1
sizeof(signed char) == 1
sizeof(unsigned char) == 1
Those three equalities are not part of any ABI. They are written into
the C standard,
[Cyril Brulebois]
> Hi,
>
> I'm wondering whether the ArchitectureSpecificsMemo[1] wiki page is
> (well-)known, and whether its content got reviewed, esp. by porters of
> each architecture, who could fix obvious errors or typos, or eventually
> add special-cases, exception
On Fri, Apr 25, 2008 at 08:12:58AM +0200, Cyril Brulebois wrote:
Hi,
I'm wondering whether the ArchitectureSpecificsMemo[1] wiki page is
(well-)known, and whether its content got reviewed, esp. by porters of
each architecture, who could fix obvious errors or typos, or eventually
add sp
Hi,
I'm wondering whether the ArchitectureSpecificsMemo[1] wiki page is
(well-)known, and whether its content got reviewed, esp. by porters of
each architecture, who could fix obvious errors or typos, or eventually
add special-cases, exceptions, and the like.
1. http://wiki.debia
15 matches
Mail list logo
