llvm dev - Feb 2005 - [LLVMdev] Re: LLVM bytecode portability

On Thu, 24 Feb 2005 23:26:53 -0600, Chris Lattner wrote:
> In the case of C/C++, basically anything that includes a 
> standard header will not be portable, at least not across systems with 
> different implementations of libc.
Do you mean portable across operating systems here, or portable across
CPU architectures? Presumably the former ...

On Fri, 25 Feb 2005, Mike Hearn wrote:
> On Thu, 24 Feb 2005 23:26:53 -0600, Chris Lattner wrote:
>> In the case of C/C++, basically anything that includes a
>> standard header will not be portable, at least not across systems with
>> different implementations of libc.
>
> Do you mean portable across operating systems here, or portable across
> CPU architectures? Presumably the former ...
Both and either.  If you include a standard system header, this will pull 
in system specific #defines and inline functions.  These won't work if you 
move to another system that doesn't match those.

-Chris

-- 
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/

On Fri, 25 Feb 2005 18:02:27 -0600, Chris Lattner wrote:
> Both and either.  If you include a standard system header, this will pull 
> in system specific #defines and inline functions.  These won't work if
you
> move to another system that doesn't match thos
Hmm, do you know of any glibc headers that pull in CPU-arch specific
code? My cunning plan of using LLVM to distribute Linux CPU-arch
independent binaries may have a slight hole if so :)

thanks -mike