From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,FROM_LOCAL_HEX,
	FROM_STARTS_WITH_NUMS autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c9d5fc258548b22a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!news.glorb.com!news2.glorb.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Vinzent Hoefler" <0439279208b62c95f1880bf0f8776eeb@t-domaingrabbing.de>
Newsgroups: comp.lang.ada
Subject: Re: How do I write directly to a memory address?
Date: Wed, 09 Feb 2011 21:44:53 +0100
Message-ID: <op.vqnk83ewlzeukk@jellix.jlfencey.com>
References: 
 <67063a5b-f588-45ea-bf22-ca4ba0196ee6@l11g2000yqb.googlegroups.com>
 <4d4ff70e$0$6886$9b4e6d93@newsspool2.arcor-online.net>
 <737a6396-72bd-4a1e-8895-7d50f287960e@d28g2000yqc.googlegroups.com>
 <4d5008a5$0$6879$9b4e6d93@newsspool2.arcor-online.net>
 <eda00084-fcc3-416c-bd3e-8b9e9c1a4b40@o13g2000yql.googlegroups.com>
 <4d5031fe$0$6765$9b4e6d93@newsspool3.arcor-online.net>
 <1f229967-d3cf-42b6-8087-c97ee08652f3@i40g2000yqh.googlegroups.com>
 <4d51169e$0$7657$9b4e6d93@newsspool1.arcor-online.net>
 <db60098c-2569-4efb-aa81-253ba53686b4@y26g2000yqd.googlegroups.com>
 <iis37l$t09$1@tornado.tornevall.net>
 <1bnp0pw1c8r5b$.guxc48qweiwe.dlg@40tude.net>
 <4d51a1c0$0$19486$882e7ee2@usenet-news.net>
 <87411ec5-c197-4143-8ef1-ab9ddb20bcc6@q40g2000prh.googlegroups.com>
 <op.vqlr2a2hlzeukk@jellix.jlfencey.com>
 <505a0855-ed01-4819-9d8e-025ad8d5cb51@y12g2000prf.googlegroups.com>
 <op.vqnffb0blzeukk@jellix.jlfencey.com> <m21v3hkl2z.fsf@pushface.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Trace: individual.net k4hNSyUmmGqywZkKK8Z92At6J48K8xS+nWrLO9OmV+xJCvEOwe
Cancel-Lock: sha1:nQFlGy2Zhd4Z0ShWav/ttboufSA=
User-Agent: Opera Mail/11.01 (Win32)
Xref: g2news2.google.com comp.lang.ada:18124
Date: 2011-02-09T21:44:53+01:00
List-Id: <comp.lang.ada>

Simon Wight wrote:

> "Vinzent Hoefler" <0439279208b62c95f1880bf0f8776eeb@t-domaingrabbing.de>
> writes:
>
>> So bit 3 of a 32-bit word is a different bit than that of a byte?
>
> Yes. On big-endian hardware.

That's a misconception, although a common one. Endianess is only defined
for bytes, that's why it's also often called byte-order.

> A 32-bit big-endian integer with bit 3 set would be 16#10_00_00_00#.

I would set 2#100#. That's independent from the byte-order and the actual
type's size.

> (You've moved the goalposts a bit; we were talking about "the third
> bit"!)

Yes. That would have been bit 2. ;)


Vinzent.

-- 
You know, we're sitting on four million pounds of fuel, one nuclear weapon,
and a thing that has 270,000 moving parts built by the lowest bidder.
Makes you feel good, doesn't it?
   --  Rockhound, "Armageddon"