[Bug testsuite/20567] dg-options in gcc.c-torture

[Bug testsuite/20567] dg-options in gcc.c-torture

[aldot at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

Bernhard Reutner-Fischer <aldot at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldot at gcc dot gnu.org

--- Comment #6 from Bernhard Reutner-Fischer <aldot at gcc dot gnu.org> 2012-03-22 13:36:09 UTC ---
(In reply to comment #4)
> The gfortran torture tests also need to support dg- options, starting with
> dg-final to allow cleaning up module files from the testsuite temporary
> directory.

implicit cleanup-modules in all gfortran related tests were recently
implemented, see testsuite/lib/fortran-modules.exp

I did not look if all torture tests pull in dg- nowadays (gcc.c-torture/compile
and gcc.c-torture/execute/ieee seem to include dg as opposed to the rest, from
a short look. Little bit of a mess, imho).
Is there consensus that all testcases should use dg (or gcc-dg) ?

[Bug testsuite/20567] dg-options in gcc.c-torture

[mrs at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
                 CC|                            |mrs at gcc dot gnu.org
         Resolution|---                         |FIXED

--- Comment #8 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> ---
Fixed.

[Bug testsuite/20567] dg-options in gcc.c-torture

[jsm28 at gcc dot gnu dot org]

------- Comment #5 from jsm28 at gcc dot gnu dot org  2008-02-07 19:52 -------
*** Bug 35126 has been marked as a duplicate of this bug. ***


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl dot tools at gmail dot
                   |                            |com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

[Bug testsuite/20567] dg-options in gcc.c-torture

[janis at gcc dot gnu dot org]

------- Comment #4 from janis at gcc dot gnu dot org  2006-03-29 17:12 -------
The gfortran torture tests also need to support dg- options, starting with
dg-final to allow cleaning up module files from the testsuite temporary
directory.


-- 

janis at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |janis at gcc dot gnu dot org
                   |dot org                     |
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2006-01-09 12:55:10         |2006-03-29 17:12:42
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

[Bug testsuite/20567] dg-options in gcc.c-torture

[janis at gcc dot gnu dot org]

------- Comment #3 from janis at gcc dot gnu dot org  2006-01-11 22:21 -------
It's easy to replace gcc.c-torture/execute/execute.exp with
compile/compile.exp, use "run" for the default instead of
"assemble", and then add test directives to the .c files to
replace the functionaity in the .x files.  There are a couple
of things that lib/c-torture.exp does that are not supported
with this:

  if the test isn't executed on native hardware, skip
  execution of a test whose binary is identical to the
  binary built with the previous set of options

  skip execution of tests that use "long long" when it
  isn't supported on the target

There are a few odd things in gcc/c-torture/execute/*.c:

  920710-1.x skips a "long long" test based on a specific
  target, but there are lots of tests that use "long long"
  and aren't skipped

  941014-1.x tries to xfail the compile step, but in a way
  where the xfail info is evaluated after the compile has
  already happened; also, it checks for either -mthumb or
  -O0; does it really want the combination?

  981130-1.x xfails the test for -O0, -O1, -O2, or -Os when
  the comment implies that it should be xfailed for -O2 or
  -O3

  990413-2.x says the test is x86 specific; should it be
  limited to ilp32?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

[Bug testsuite/20567] dg-options in gcc.c-torture

[jsm28 at gcc dot gnu dot org]

------- Additional Comments From jsm28 at gcc dot gnu dot org  2005-06-05 11:32 -------
Also note <http://gcc.gnu.org/ml/gcc-patches/2005-06/msg00358.html> and followup:

20050603-1.c and 20050603-2.c have been added in gcc.c-torture/execute using dg-do.

gcc.c-torture/compile/20030405-1.x shouldn't be there; dg-options in the
testcase should be used instead.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567

[Bug testsuite/20567] dg-options in gcc.c-torture

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-03-20 17:48 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-03-20 17:48:29
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567