This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, 2006-01-04 at 19:07, Lennert Buytenhek wrote: > Hi all, > > The attached patch allows building an arm AAPCS toolchain with gcc 4.0. > However.. the resulting object files and binaries are marked as APCS-32, > which is incorrect: > > $ arm-aapcs-linux-gnu-gcc -Wall -o xx xx.c > $ arm-aapcs-linux-gnu-objdump --all xx | grep ^private > private flags = 2: [APCS-32] [FPA float format] [has entry point] > $ > > Phil Blundell suggested that this is probably because binutils (as) didn't > have flags for passing the ABI type when the gcc 4.0 branch was forked > off. Partially because of this, trying to use gcc 4.0 for anything EABI > is kind of a dead end (as he already said.) FYI. The GCC 4.0 sources are missing MANY MANY patches for EABI/AAPCS support. Please don't try to go there, or you'll end up with binaries which are subtly (or maybe even grossly) broken. If you want to try building an AAPCS compiler, grab a pre-release of gcc-4.1 or one of the CodeSourcery distributions of gcc-3.4 (you can get source if you need it). R. ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |