[M3devel] posix/nt/32/64/endian platforms for C backend?

[Jay K]

But if these are new targets, that can only generate C?I claim the endianness is arbitrary and only serves for interop with C bitfields and nothing else.It doesn't matter what endianness you declare. It is likely to work correctly either way.I have to double check that integers and floats are initialized "at once", and not a byte at a time.
 - Jay



> Subject: Re: [M3devel] posix/nt/32/64/endian platforms for C backend?
> From: hosking at purdue.edu
> Date: Mon, 17 Aug 2015 09:49:37 +1000
> CC: m3devel at elegosoft.com
> To: jay.krell at cornell.edu
> 
> I strongly prefer that the front-end remain aware of target endianness (as it currently is for packing/unpacking bits in memory).
> It is important that there be some correspondence with the target.
> So, endianness should remain.
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150817/35af5546/attachment-0002.html>