From: Janis Johnson <janis_johnson@mentor.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: <janisjo@codesourcery.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Fix PR 54033, problems with -I
Date: Fri, 27 Jul 2012 22:15:00 -0000 [thread overview]
Message-ID: <50130F9B.1010300@mentor.com> (raw)
In-Reply-To: <5012F4AF.7050807@netcologne.de>
On 07/27/2012 01:06 PM, Thomas Koenig wrote:
> Hi Janis,
>
>> On 07/26/2012 10:16 AM, Thomas Koenig wrote:
>>
>>> No test case because I couldn't figure out how to test for a
>>> warning with no line number.
>>
>> Try using line number 0.
>
> That didn't work for me. Using
>
> ! { dg-do compile }
> ! { dg-options "-I include_6.f90 -I missing_dir" }
> ! { dg-warning "not a directory" "missing directory" target *-*-* 0 }
> ! { dg-warning "does not exist" "nonexisting directory" target *-*-* 0 }
> end
>
> got me
>
> Warning: Include directory "include_6.f90" does not exist^M
> Warning: Include directory "missing_dir" does not exist^M
> output is:
> Warning: Include directory "include_6.f90" does not exist^M
> Warning: Include directory "missing_dir" does not exist^M
>
> FAIL: gfortran.dg/include_6.f90 -O (test for excess errors)
> Excess errors:
> :0:0: Warning: Include directory "include_6.f90" does not exist
> :0:0: Warning: Include directory "missing_dir" does not exist
Use "{ target *-*-* }" instead of "target *-*-*".
Notice that the two warnings have the same text, so the directive
looking for "not a directory" will fail.
Janis
next prev parent reply other threads:[~2012-07-27 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 17:16 Thomas Koenig
2012-07-26 18:20 ` Janis Johnson
2012-07-27 20:31 ` Thomas Koenig
2012-07-27 22:15 ` Janis Johnson [this message]
2012-07-29 12:00 ` [patch, fortran] Fix PR 54033, problems with -I, with test cases Thomas Koenig
2012-07-31 13:50 ` Tobias Burnus
2012-08-02 8:54 ` Richard Guenther
2012-08-02 9:41 ` Tobias Burnus
2012-08-02 20:08 ` Thomas Koenig
2012-08-03 17:10 ` Thomas Koenig
2012-08-04 17:31 ` H.J. Lu
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=50130F9B.1010300@mentor.com \
--to=janis_johnson@mentor.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@codesourcery.com \
--cc=tkoenig@netcologne.de \
/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).