From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26641 invoked by alias); 13 Jan 2013 23:11:08 -0000 Received: (qmail 26631 invoked by uid 22791); 13 Jan 2013 23:11:07 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 13 Jan 2013 23:10:35 +0000 Received: from mailout-de.gmx.net ([10.1.76.4]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Mee1e-1TalpB2pdg-00OFpw for ; Mon, 14 Jan 2013 00:10:33 +0100 Received: (qmail invoked by alias); 13 Jan 2013 23:10:33 -0000 Received: from adsl-84-227-65-110.adslplus.ch (EHLO manfred-laptop.site) [84.227.65.110] by mail.gmx.net (mp004) with SMTP; 14 Jan 2013 00:10:33 +0100 Message-ID: <50F33EE7.5000200@gmx.ch> Date: Sun, 13 Jan 2013 23:11:00 -0000 From: Manfred Schwarb User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: Harald Anlauf CC: Mikael Morin , fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: testsuite: missing or wrong dg-* directives? References: <50DE05CF.4070900@gmx.de> <50EC9065.7000801@gmx.de> <50F1CF62.4020901@sfr.fr> <50F31967.4050003@gmx.de> In-Reply-To: <50F31967.4050003@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg00671.txt.bz2 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. 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 > > * 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. >