toolchain's output depends on toolchain used to build the compiler?
Omer Zak
w1 at zak.co.il
Tue Feb 9 23:07:27 IST 2010
I suggested before to check the compiler and linker flags which are
actually used.
Now I decided to check how to actually make the checks.
According to man gcc:
-v (verbose mode) reports the final form of the include path.
--help -v reports extra information which can be helpful.
I found that for example:
gcc --help -v 2>&1 | less
when run under Linux (Debian Lenny), displays - among lots of other
information - the flags passed
to /usr/lib/gcc/i486-linux-gnu/4.3.2/collect2 (my gcc version is 4.3.2).
DISCLAIMER:
I did not check the above when invoked by makefiles with custom
compile-time flags. Therefore, YMMV.
--- Omer
On Tue, 2010-02-09 at 22:08 +0200, Shachar Shemesh wrote:
> Oleg Goldshmidt wrote:
> >
> >
> > 2010/2/9 Shachar Shemesh <shachar at shemesh.biz>
> >
> > The newlib libraries built are compared, and are identical
> > down to the last assembly instruction. The client libraries
> > are compared. Some are identical, some are not.
> >
> >
> > Just to dot all the i's and cross all the t's: are the
> > cross-binutils identical?
> >
> As listed in the table that started the thread, they are compiled as
> part of the compiler bring up. In other words, yes.
>
> Shachar
--
Philip Machanick: "caution: if you write code like this, immediately
after you are fired the person assigned to maintaining your code after
you leave will resign"
My own blog is at http://www.zak.co.il/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which
I may be affiliated in any way.
WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
More information about the Linux-il
mailing list