This is the mail archive of the crossgcc@sources.redhat.com 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] |
We've found the problem. Turns out our build script was to blame, not the patches. We were executing a loop like:
for cpu in sh4 i686 powerpc-405 powerpc-750; do
cd $TOP_DIR
# Load definitions for current CPU into environment and build eval `cat $cpu.dat ../$TOOLCOMBO.dat` buildit done
Interestingly, this behaves differently if executed with /bin/sh instead of /bin/bash. In the former case, any variables set by $cpu.dat are preserved between iterations. In the latter case, they are only valid for a single execution of buildit.
We were all executing the script with "sh ./doit.sh", which was causing the ppc750 build to give weird floating point results *only* if it was built after sh4 and powerpc-405.
Aha! OK, that explains a lot. Maybe I'll include a note in the doc about this.
------ 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] |