Re: Implementation of ARM EABI library requirements?

[Mark Mitchell <mark at codesourcery dot com>]

Duane Ellis wrote:

> My quick glance at the ARM doc - I did not see any thing about "libgcc"
> like functions.
> Division, floating Point, etc, That's not newlib - that is a GCC issue.

Yes, and specified in the rest of the ARM ABI -- and already implemented
in GCC.

> I also did not see things about #defines for example - flag bits for
> mode in the open() call.

The ARM library ABI only deals with ISO C.  So, "open" (which is POSIX,
but not ISO), is not covered.  But, in general, #defines are dealt with
by externalizing them as variables.  I'm not sure why you think that's
particularly messy; it's just things like:

  int __aeabi_FOO = FOO;

and then:

  #ifdef _AEABI_PORTABLE
  #define FOO __aeabi_FOO
  #endif

in the headers.

> Then there are structure alignment, structure padding, etc issues across
> compilers.

Again, already specified in the ARM ABI and already implemented in GCC.

> I wonder if these changes *ALSO* dictate changes on the compiler command
> line?

No.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713