[M3devel] thread local storage, but in C pieces of runtime... (jay, tony?)

[Jay K]

 > Portable .i3 files would be a bit easier if you > did not insist on pointer alignment of 64 on platform   No that is not the problem.Sorry, I didn't mean portable .i3 files in general.I meant portable .i3 file that match the Posix implementation on any systems..i3 files backed by .m3 or backed by one C implementation are "portable".That is how we bridge to Posix now -- .i3 files that describe our own C, that isn't #ifdefed at all.  Dragisa, do you mean to say that Posix describes an ABI? It does not.It does not describe a "binary" interface, only a source interface.C code can call "open", but "open" does not necessarily exist in any .o or .a file.It can be #defined to something else, or renamed with a compiler-specific #pragma.I have seen both, not long ago, on mainstream systems. NetBSD comes to mind. And Solaris. And Linux (esp. wrt stat). And Darwin.   - Jay Subject: Re: [M3devel] thread local storage, but in C pieces of runtime... (jay, tony?)
From: dragisha at m3w.org
Date: Fri, 10 May 2013 21:31:20 +0200
CC: mika at async.caltech.edu; m3devel at elegosoft.com
To: jay.krell at cornell.edu

Yes, POSIX defines it, and then usually does not change it every now and then.
Portable .i3 files would be a bit easier if you did not insist on pointer alignment of 64 on platform where 32bit is a standard :). Bit packing gives enough control over how struct is being made with only problem there being insistence on 64bit alignment for pointers, although it can be controlled with BITS .. FOR. 
As for m3core mess, and it was lots of it, you are right and work you two did is great.

--Dragiša Durićdragisha at m3w.org



On May 10, 2013, at 8:03 PM, Jay K wrote:Posix defines a C source interface, not an ABI.

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130510/6439e668/attachment-0002.html>