public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Schwarb <manfred99@gmx.ch>
To: Harald Anlauf <anlauf@gmx.de>
Cc: Mikael Morin <mikael.morin@sfr.fr>,
	fortran@gcc.gnu.org,  gcc-patches@gcc.gnu.org
Subject: Re: testsuite: missing or wrong dg-* directives?
Date: Sun, 13 Jan 2013 23:38:00 -0000	[thread overview]
Message-ID: <50F34546.9080807@gmx.ch> (raw)
In-Reply-To: <50F33EE7.5000200@gmx.ch>

Am 14.01.2013 00:10, schrieb Manfred Schwarb:
> Am 13.01.2013 21:30, schrieb Harald Anlauf:
>> On 01/12/13 22:02, Mikael Morin wrote:
>>> Le 08/01/2013 22:32, Harald Anlauf a écrit :
>>>> On 12/28/12 21:49, Harald Anlauf wrote:
>>>>> Hello all,
>>>>>
>>>>> is there a default directive that is assumed when the testsuite is run?
>>>>>
>>>>> Running an "fgrep -L" on the fortran testsuite, I found several files
>>>>> that are missing either dg-do compile or run.
>>>>>
>>>>> I also found a funny typo in gomp/appendix-a/a.11.2.f90
>>>>> ! { do-do compile }
>>>>
>
> There are several other oddities: d_g-final, braces have to be separated by spaces.
> Not sure about the double braces in lto, I guess they act simply as single braces.
>


Oh, and then there is the "dg-do  run" hack (two spaces, see cray_pointers_2.f90).
I guess the other occurrences are not intended:

default_initialization_5.f90:! { dg-do  run }
io_real_boz_3.f90:! { dg-do  run }
io_real_boz_4.f90:! { dg-do  run }
io_real_boz_5.f90:! { dg-do  run }


> class_array_10.f03:! { dg-do compile}
> coarray_lib_token_4.f90:! { d_g-final { scan-tree-dump-times "bar \\(&parm.\[0-9\]+, caf_token.\[0-9\]+, \\(\\(integer\\(kind=.\\) parm.\[0-9\]+.data - \\(integer\\(kind=.\\)\\) x.\[0-9\]+\\) \\+ caf_offset.\[0-9\]+\\);" 1 "original" } }
> continuation_9.f90:! { dg-warning "not allowed by itself in line 3" "" {target "*-*-*"} 0 }
> continuation_9.f90:! { dg-warning "not allowed by itself in line 4" "" {target "*-*-*"} 0 }
> continuation_9.f90:! { dg-warning "not allowed by itself in line 5" "" {target "*-*-*"} 0 }
> extends_11.f03:! { dg-final { scan-tree-dump-times " +recruit\\.service\\.education\\.person\\.ss =" 8 "original"} }
> lto/20091016-1_0.f90:! { dg-lto-options {{-flto -g -fPIC -r -nostdlib} {-O -flto -g -fPIC -r -nostdlib}} }
> lto/20100110-1_0.f90:! { dg-lto-options {{ -O1 -flto }} }
> lto/pr41521_0.f90:! { dg-lto-options {{-g -flto} {-g -O -flto}} }
> lto/pr46036_0.f90:! { dg-lto-options {{ -O -flto -ftree-vectorize }} }
> lto/pr46629_0.f90:! { dg-lto-options {{ -O2 -flto -ftree-vectorize -march=x86-64 }} { target i?86-*-* x86_64-*-* } }
> lto/pr46629_0.f90:! { dg-lto-options {{ -O2 -flto -ftree-vectorize }} }
> lto/pr46911_0.f:! { dg-lto-options {{ -O2 -flto -g }} }
> lto/pr47839_0.f90:! { dg-lto-options {{ -g -flto }} }
> move_alloc_13.f90:! { dg-do run}
> structure_constructor_11.f90:! { dg-do run}
> tab_continuation.f:! { dg-warning "Nonconforming tab character in column 1 of line 10" "Nonconforming tab" {target "*-*-*"} 0 }
> tab_continuation.f:! { dg-warning "Nonconforming tab character in column 1 of line 11" "Nonconforming tab" {target "*-*-*"} 0 }
> tab_continuation.f:! { dg-warning "Nonconforming tab character in column 1 of line 8" "Nonconforming tab" {target "*-*-*"} 0 }
> tab_continuation.f:! { dg-warning "Nonconforming tab character in column 1 of line 9" "Nonconforming tab" {target "*-*-*"} 0 }
> vect/vect-2.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using versioning." 3 "vect" {target { vect_no_align || { { ! vector_alignment_reachable  } && { ! vect_hw_misalign } } } } } }
> vect/vect-3.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 1 "vect" { xfail { vect_no_align || {! vector_alignment_reachable}} } } }
> vect/vect-3.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using versioning" 1 "vect" { target { {! vect_no_align} && { {! vector_alignment_reachable} && {! vect_hw_misalign} } } } } }
> vect/vect-3.f90:! { dg-final { scan-tree-dump-times "Vectorizing an unaligned access" 1 "vect" { xfail { { vect_no_align } || { ! vector_alignment_reachable} } } } }
> vect/vect-3.f90:! { dg-final { scan-tree-dump-times "Vectorizing an unaligned access" 2 "vect" { target { {! vect_no_align} && { {! vector_alignment_reachable} && {! vect_hw_misalign} } } } } }
> vect/vect-4.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 1 "vect" { xfail { { vect_no_align } || {! vector_alignment_reachable} } } } }
> vect/vect-4.f90:! { dg-final { scan-tree-dump-times "Vectorizing an unaligned access" 1 "vect" { xfail { { vect_no_align } || {! vector_alignment_reachable} } } } }
> vect/vect-4.f90:! { dg-final { scan-tree-dump-times "Vectorizing an unaligned access" 2 "vect" { target { {! vector_alignment_reachable} && {! vect_hw_misalign} } } } }
> vect/vect-5.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 1 "vect" { xfail { vect_no_align || {! vector_alignment_reachable} } } } }
> vect/vect-5.f90:! { dg-final { scan-tree-dump-times "Alignment of access forced using versioning." 1 "vect" { target { {! vector_alignment_reachable} && {! vect_hw_misalign} } } } }
> warning-directive-2.F90:! { dg-message "some warnings being treated as errors" "" {target "*-*-*"} 0 }
>
>
> cheers,
> Manfred
>
>
>
>>>> find gfortran.dg -name "*.[fF]90" -o -name "*.[fF]" | \
>>>> xargs fgrep -w -L 'dg-do' | \
>>>> xargs head -1 -v
>>>>
>>>> and manual inspection of the resulting output results in:
>>>>
>>>> - Typos
>>>>
>>> [...]
>>>>
>>>> - Possibly missing { dg-do run }
>>>>
>>> [...]
>>>
>>> Mind sending patch and changelog to @gcc-patches ?
>>>
>>
>> Here we go.  No failures, but additional passes because of the dg-do run's.  Somebody please take care of it?
>>
>> Harald
>>
>>
>> 2013-01-13  Harald Anlauf <anlauf@gmx.de>
>>
>>      * gfortran.dg/aint_anint_1.f90: Add dg-do run.
>>      * gfortran.dg/bounds_check_4.f90: Likewise.
>>      * gfortran.dg/inquire_10.f90: Likewise.
>>      * gfortran.dg/minloc_3.f90: Likewise.
>>      * gfortran.dg/minlocval_3.f90: Likewise.
>>      * gfortran.dg/module_double_reuse.f90: Likewise.
>>      * gfortran.dg/mvbits_1.f90: Likewise.
>>      * gfortran.dg/oldstyle_1.f90: Likewise.
>>      * gfortran.dg/pr20163-2.f: Likewise.
>>      * gfortran.dg/save_1.f90: Likewise.
>>      * gfortran.dg/scan_1.f90: Likewise.
>>      * gfortran.dg/select_char_1.f90: Likewise.
>>      * gfortran.dg/shape_4.f90: Likewise.
>>      * gfortran.dg/coarray_29_2.f90: Fix dg-do directive.
>>      * gfortran.dg/function_optimize_10.f90: Likewise.
>>      * gfortran.dg/gomp/appendix-a/a.11.2.f90: Likewise.
>>      * gfortran.dg/used_types_17.f90: Likewise.
>>      * gfortran.dg/used_types_18.f90: Likewise.
>>
>
>

  reply	other threads:[~2013-01-13 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50DE05CF.4070900@gmx.de>
     [not found] ` <50EC9065.7000801@gmx.de>
     [not found]   ` <50F1CF62.4020901@sfr.fr>
2013-01-13 20:30     ` Harald Anlauf
2013-01-13 23:11       ` Manfred Schwarb
2013-01-13 23:38         ` Manfred Schwarb [this message]
2013-01-14 14:23           ` Mikael Morin
2013-01-14 19:49             ` Mike Stump
2013-01-15 21:47               ` Manfred Schwarb
2013-01-14 22:16         ` Harald Anlauf
2013-01-15 21:22           ` Mikael Morin
2013-01-15 21:30           ` Manfred Schwarb
2013-01-14 14:05       ` Mikael Morin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50F34546.9080807@gmx.ch \
    --to=manfred99@gmx.ch \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikael.morin@sfr.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).