Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff
tags 814978 patch
thanks
On Wed, 2016-02-17 at 12:06 +0100, Svante Signell wrote:
> On Wed, 2016-02-17 at 11:50 +0100, Matthias Klose wrote:
> > On 17.02.2016 10:31, Svante Signell wrote:
> > > Source: gcc-5
> > > Version: 5.3.1-8
> > > Severity: important
> > > Usertags: gnat-5
>
> > this might be a bad merge/update; Ludovic, Nicolas, could you have a look?
> > GCC
> > 6
> > likely has the same issue.
>
> Yes, the problem is the same for gcc-6. One effect of this problem is that the
> acats tests fail ro run (all architectures).
Hi, it seems that the src/gcc/testsuite/ada/acats/run_all.sh script for the
acats tests has a bug in addition to the gnatchop gcc-5-5 bug, currently worked
around by soft linking gcc-5 to gcc-5-5.
The remaining problem is a carriage return character in the target_bit variable,
fixed by the patch:
--- a/src/gcc/testsuite/ada/acats/run_all.sh.orig 2016-02-17 17:29:12.872370832 +0100
+++ b/src/gcc/testsuite/ada/acats/run_all.sh 2016-02-18 12:09:48.636362809 +0100
@@ -136,7 +136,7 @@
# Find out the size in bit of an address on the target
target_gnatmake $testdir/support/impbit.adb >> $dir/acats.log 2>&1
target_run $dir/support/impbit > $dir/support/impbit.out 2>&1
-target_bit=`cat $dir/support/impbit.out`
+target_bit=`cat $dir/support/impbit.out` | sed -e 's/\r//g'
echo target_bit="$target_bit" >> $dir/acats.log
# Find out a suitable asm statement
The acats tests then run fine; on amd64 the result is:
=== acats Summary ===
# of expected passes 2256
# of unexpected failures 49
*** FAILURES: cd10001 cd2a83c cd2a91c cd30001 cd5003a cd5003b cd5003c cd5003d
cd5003e cd5003f cd5003g cd5003h cd5003i cd5011a cd5011c cd5011e cd5011g cd5011i
cd5011k cd5011m cd5011q cd5011s cd5012a cd5012b cd5012e cd5012f cd5012i cd5012m
cd5013a cd5013c cd5013e cd5013g cd5013i cd5013k cd5013m cd5013o cd5014a cd5014c
cd5014e cd5014g cd5014i cd5014k cd5014m cd5014o cd5014t cd5014v cd5014x cd5014y
cd5014z
Reply to: