Run the ACATS on a ZFP runtime

2013-04-09 Thread PARAT Didier
Hi,

I want to run the Ada Conformity Assessment Test Suite in 
gcc/testsuite/ada/acats on a ZFP runtime.
But the ACATS uses packages such as ADA.TEXT_IO which are not available on a 
ZFP runtime.
Is there any way to configure the ACATS for a ZFP runtime environment? 

I use GCC 4.5.2.

Cheers.


gnat.dg test: div_no_warning.adb

2014-02-12 Thread PARAT Didier
Hi,

I'm trying to use the tests in "gcc/testsuite/gnat.dg" and I'm having trouble 
understanding one particular test: "gnat.dg/div_no_warning.adb". If I 
understand correctly, this test is expected to compile without any error or 
warning. When I compile this test with a native compiler gnatmake, I get no 
error nor warning. But when I compile it with a gcc port to private target I 
get the following output:

div_no_warning.adb:13:20: warning: division by zero
div_no_warning.adb:13:20: warning: "Constraint_Error" will be raised at run time

The source looks like:
.
4  :    Flag : constant Boolean := False;
.
12:   if Flag and then F then
13:  Int := Int / 0;
14:   end if;
.

I checked the assembler produced by my compiler, it does not contain any code 
corresponding to the division or "if" code shown before. So I guess the 
compiler has detected that the "if False and then ." is dead code, but still I 
get the warnings.

I'm having a hard time finding what kind of option is activated/suppressed in 
the native compiler so it does not output those warnings.

I'm working on GCC 4.7.3 and GNAT 7.1.2.

Any help appreciated.

Thanks,
Didier


Using DejaGNU on GCC's Testsuite

2012-08-20 Thread PARAT Didier
Hi,

I am using DejaGNU on GCC's Testsuite and a problem appeared to me, some tests 
fail when they shouldn't be.

For example: The test gcc.dg/pr27528.c has the line " /* { dg-options "" } */ " 
which means that this test should be compiled without any options, right? But 
DejaGNU seems to pass some basic options anyway (for ex. -O1, -O2, etc...) and 
this causes the test to fail because it is meant to be tested without 
optimizations.

I saw this problem with a lot more testcases causing them to have two 
optimization level in the same command line "gcc ... -O1 -O2 -o ...". This 
problem seems to happen when the testcase has some specific options in the line 
dg_options, for ex. " /* { dg-options "-O2" } */ ".

Did anyone ever try to run the GCC testsuite with DejaGNU and notice this kind 
of things?

I'm using DejaGNU 1.5

Thanks,
Didier


RE: Using DejaGNU on GCC's Testsuite

2012-08-21 Thread PARAT Didier

Thanks, but how come nobody noticed that some of these tests
(gcc.dg/pr27528.c and some others) needed the line 
{ dg-options "-O0" } instead of { dg-options "" } ?

- 
From : Jonathan Wakely
On : 20/08/2012

On 20/08/2012, PARAT Didier  wrote:
> Hi,
>
> I am using DejaGNU on GCC's Testsuite and a problem appeared to me, some
> tests fail when they shouldn't be.
>
> For example: The test gcc.dg/pr27528.c has the line " /* { dg-options "" }
> */ " which means that this test should be compiled without any options,
> right?

Wrong. It means an empty string should be appended to the list of
default optio.s (at least that's what it means for libstdc++ tests,
where the defaults come from scripts/testsuite_flags)

> But DejaGNU seems to pass some basic options anyway (for ex. -O1,
> -O2, etc...) and this causes the test to fail because it is meant to be
> tested without optimizations.
 Then maybe it should use { dg-options "-O0" }

> I saw this problem with a lot more testcases causing them to have two
> optimization level in the same command line "gcc ... -O1 -O2 -o ...". This
> problem seems to happen when the testcase has some specific options in the
> line dg_options, for ex. " /* { dg-options "-O2" } */ ".

That's not a problem, the last -On option overrides any earlier ones.

> Did anyone ever try to run the GCC testsuite with DejaGNU and notice this
> kind of things?
>
> I'm using DejaGNU 1.5
>
> Thanks,
> Didier
>
-


RE: Using DejaGNU on GCC's Testsuite

2012-08-21 Thread PARAT Didier
If no options are passed to DejaGNU for the GCC testsuite,
it will take default ones in testsuite/lib/gcc-dg.exp and 
testsuite/lib/c-torture.exp. So 'dg' tests, as well as c-torture,
use basic options.

By the way, I'm working on gcc-4.5.2 (gnat-6.4.2)

- 
From : Andreas Schwab
On 21/08/2012

PARAT Didier  writes:

> For example: The test gcc.dg/pr27528.c has the line " /* { dg-options
> "" } */ " which means that this test should be compiled without any
> options, right? But DejaGNU seems to pass some basic options anyway
> (for ex. -O1, -O2, etc...)

Does it?  Only c-torture tests normally do that.  What does the testuite
log file says for that test?

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-