gm2
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Catching up, some old some new problems. test errors?


From: Gaius Mulley
Subject: Re: Catching up, some old some new problems. test errors?
Date: Mon, 04 May 2020 09:36:34 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Dragiša Durić <address@hidden> writes:

> On Sun, 2020-05-03 at 12:43 +0100, Gaius Mulley wrote:
>> I get 1 error from building gm2 master branch on a x86_64 debian
>> stretch
>> system and no errors using gm2 master on aarch64 debian stretch.
>
> On an RPi, gm2 configured with
>
> ../gcc-versionno/configure --enable-languages=c,c++,gm2 --disable-multilib 
> --disable-bootstrap --prefix=/opt/local -with-cpu=cor^Cx-a53 
> --with-fpu=neon-fp-armv8 --with-float=hard --build=arm-linux-gnueabihf
>
> built, run checks. Results:
>
> Test run by pi on Sun May  3 14:51:21 2020
> Native configuration is arm-unknown-linux-gnueabihf
>
>               === gm2 tests ===
>
> Schedule of variations:
>     unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using 
> /home/pi/extra/gm2/scratch/sources/gm2/gcc-versionno/gcc/testsuite/config/default.exp
>  as tool-and-target-specific interface file.
> .....
> FAIL: gm2/errors/fail/array1.mod,  -g  
> FAIL: gm2/errors/fail/array1.mod,  -O  
> FAIL: gm2/errors/fail/array1.mod,  -O -g  
> FAIL: gm2/errors/fail/array1.mod,  -Os  
> FAIL: gm2/errors/fail/array1.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/errors/fail/array1.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> FAIL: gm2/errors/fail/proctype.mod,  -g  
> FAIL: gm2/errors/fail/proctype.mod,  -O  
> FAIL: gm2/errors/fail/proctype.mod,  -O -g  
> FAIL: gm2/errors/fail/proctype.mod,  -Os  
> FAIL: gm2/errors/fail/proctype.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/errors/fail/proctype.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> FAIL: gm2/errors/fail/testbit2.mod,  -g  
> FAIL: gm2/errors/fail/testbit2.mod,  -O  
> FAIL: gm2/errors/fail/testbit2.mod,  -O -g  
> FAIL: gm2/errors/fail/testbit2.mod,  -Os  
> FAIL: gm2/errors/fail/testbit2.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/errors/fail/testbit2.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> FAIL: gm2/errors/fail/testfio.mod,  -g  
> FAIL: gm2/errors/fail/testfio.mod,  -O  
> FAIL: gm2/errors/fail/testfio.mod,  -O -g  
> FAIL: gm2/errors/fail/testfio.mod,  -Os  
> FAIL: gm2/errors/fail/testfio.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/errors/fail/testfio.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> FAIL: gm2/errors/fail/testparam.mod,  -g  
> FAIL: gm2/errors/fail/testparam.mod,  -O  
> FAIL: gm2/errors/fail/testparam.mod,  -O -g  
> FAIL: gm2/errors/fail/testparam.mod,  -Os  
> FAIL: gm2/errors/fail/testparam.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/errors/fail/testparam.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> .....
> FAIL: gm2/iso/run/pass/long2.mod execution,  -g 
> FAIL: gm2/iso/run/pass/long2.mod execution,  -O 
> FAIL: gm2/iso/run/pass/long2.mod execution,  -O -g 
> FAIL: gm2/iso/run/pass/long2.mod execution,  -Os 
> FAIL: gm2/iso/run/pass/long2.mod execution,  -O3 -fomit-frame-pointer 
> FAIL: gm2/iso/run/pass/long2.mod execution,  -O3 -fomit-frame-pointer 
> -finline-functions 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -g 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -O 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -O -g 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -Os 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -O3 -fomit-frame-pointer 
> FAIL: gm2/iso/run/pass/long3.mod execution,  -O3 -fomit-frame-pointer 
> -finline-functions 
> .....
> FAIL: gm2/pim/fail/TestLong4.mod,  -g  
> FAIL: gm2/pim/fail/TestLong4.mod,  -O  
> FAIL: gm2/pim/fail/TestLong4.mod,  -O -g  
> FAIL: gm2/pim/fail/TestLong4.mod,  -Os  
> FAIL: gm2/pim/fail/TestLong4.mod,  -O3 -fomit-frame-pointer  
> FAIL: gm2/pim/fail/TestLong4.mod,  -O3 -fomit-frame-pointer 
> -finline-functions  
> .....
> FAIL: gm2/pim/run/pass/integer.mod execution,  -g 
> FAIL: gm2/pim/run/pass/integer.mod execution,  -O 
> FAIL: gm2/pim/run/pass/integer.mod execution,  -O -g 
> FAIL: gm2/pim/run/pass/integer.mod execution,  -Os 
> FAIL: gm2/pim/run/pass/integer.mod execution,  -O3 -fomit-frame-pointer 
> FAIL: gm2/pim/run/pass/integer.mod execution,  -O3 -fomit-frame-pointer 
> -finline-functions 
> .....
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -g 
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -O 
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -O -g 
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -Os 
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -O3 
> -fomit-frame-pointer 
> FAIL: gm2/pimlib/base/run/pass/testconvert.mod execution,  -O3 
> -fomit-frame-pointer -finline-functions 
> .....
>
>               === gm2 Summary ===
>
> # of expected passes          11756
> # of unexpected failures      60

Hi Dragiša,

it might be worth trying the gm2 master branch - a number of the above
regression tests (integer.mod), (proctype.mod), were fixed by
substantial code additions to the compiler.

Perhaps apple and oranges comparison - but on the gm2 master branch on
an aarch64 using these configure options

--prefix=/home/gaius/opt --libexecdir=/home/gaius/opt/lib
  --enable-threads=posix --enable-clocale=gnu
  --enable-languages=c,c++,m2 --enable-multilib --disable-bootstrap
  --enable-checking --program-suffix=-6
  --program-prefix=arm-linux-gnueabihf- --disable-bootstrap
  --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf
  --target=arm-linux-gnueabihf --with-arch-directory=arm
  --disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16
  --with-float=hard --enable-long-longx

I get no regression test errors

regards,
Gaius



reply via email to

[Prev in Thread] Current Thread [Next in Thread]