This is the mail archive of the
mailing list for the GCC project.
RE: Triple name
- From: "Mile Davidovic" <mile dot davidovic at micronasnit dot com>
- To: "'Ian Lance Taylor'" <ian at airs dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Wed, 2 Feb 2005 15:15:52 +0100
- Subject: RE: Triple name
- Organization: MicronasNIT
- Reply-to: <mile dot davidovic at micronasnit dot com>
>> But I have second question, what is about libraries and object files
>> (crtbegin.o, crtend.o, crti.o, crtn.o and libgcc.a) which is created
>> during building cross compiler? Is it possible to have calling
>> convention collision?
>Yes. You need to make sure that everything is built with the same calling
>> We are using newlib as standard library, is it possible to use same
>> one for both compilers, I guess not?
>It is if you are careful to build everything with the same calling
>Perhaps I should have asked this first, but: why do you want to do this?
Why not just pick one toolchain and use it? Use the appropriate
>mips option to pick which CPU you want to build for, and everything will
> You may also want to consider configuring using --with-arch and/or
I want to use same compiler for different targets( one is mips1 and second
is mips32). Currently I have one compiler for each target.
Unfortunately mipsisa32-elf-gcc use EABI as default ABI and mips-elf-gcc use
ABI32. I know that I can select arch and abi (with --with-arch and/or
--with-abi) but problem is with libgcc and crt stuff which is I think
different for both target.
Best regards Mile