On Wed, Mar 7, 2012 at 8:01 AM, Ulrich Weigand <ulrich.weig...@de.ibm.com> wrote: > Ramana Radhakrishnan <ramana.radhakrish...@linaro.org> wrote: > >> Is it possible that the version string has the name of the branch ? >> That's the only thing I can think of that could be different and could >> cause this problem. >> >> In this : >> http://ex.seabright.co.nz/build/gcc-linaro-4.7 >> +bzr114970~uweigand~usatssat-4.7/logs/x86_64-natty-cbuild259-oort1- >> x86_64r1/gcc-testsuite.txt >> >> I see - >> >> /scratch/cbuild/slave/slaves/oort1/gcc-linaro-4.7 >> +bzr114970~uweigand~usatssat-4.7/gcc/default/build/gcc/xgcc >> version 4.7.0 20120214 (experimental) [gcc-linaro/usatssat-4.7 >> revision 114970] (GCC) >> >> Is it the version string rather than the directory name ? > > Ah, good catch! This would certainly explain it, since the > version string appears in the assembler source via the .ident > directive the compiler always adds ... > > I guess one could try to change the testsuite scripts to ignore > .ident for scan-assembler purposes. But a much simpler fix seems > to be to just not add the branch name to the version string when > building the compiler in the first place; since those compilers > are just used for testing, it doesn't really seem necessary. > > Michael, any thoughts on this?
(LP: #913997) I use a modified stamp_branch.sh when exporting the merge request which sets the branch to gcc-linaro/branch-name. I've modified this and fired a test run with 'cmp' in the name which historically fails on x86_64 and i686. Let's see how it goes... -- Michael _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
