From: "VandeVondele Joost" <joost.vandevondele@mat.ethz.ch>
To: Dominique Dhumieres <dominiq@lps.ens.fr>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Cc: "jakub@redhat.com" <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH, Fortran] PR61234: -Wuse-no-only
Date: Wed, 30 Jul 2014 14:24:00 -0000 [thread overview]
Message-ID: <908103EDB4893A42920B21D3568BFD930CCD9D24@MBX23.d.ethz.ch> (raw)
In-Reply-To: <20140610100904.7233E105@mailhost.lps.ens.fr>
>> This explicitly tests that no bogus error message is issued
>> for a use statement that has an only qualifier ?
>
>I don't see the need for '! { dg-bogus "has no ONLY qualifier" }'.
>AFAICT there is no warning emitted for this line (unless you add -Wall)
>and if some day it happens that an error/warning is issued, the test will fail.
>
>Otherwise the new patch is OK for me.
if so, could the patch be applied by somebody with svn write permission (with or without the dg-bogus), fsf assignment is now OK.
Joost
next prev parent reply other threads:[~2014-07-30 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 9:07 Dominique Dhumieres
2014-06-02 5:48 ` VandeVondele Joost
2014-06-10 10:09 ` Dominique Dhumieres
2014-07-30 14:24 ` VandeVondele Joost [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 13:13 Tobias Burnus
2014-08-22 10:16 ` VandeVondele Joost
2014-08-19 11:41 Dominique Dhumieres
2014-08-19 11:44 ` VandeVondele Joost
2014-06-02 20:08 FX
2014-05-30 8:03 VandeVondele Joost
2014-05-30 9:20 ` Jakub Jelinek
2014-05-30 9:32 ` VandeVondele Joost
2014-06-10 7:14 ` VandeVondele Joost
2014-08-18 15:51 ` VandeVondele Joost
2014-08-18 16:02 ` Manuel López-Ibáñez
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=908103EDB4893A42920B21D3568BFD930CCD9D24@MBX23.d.ethz.ch \
--to=joost.vandevondele@mat.ethz.ch \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).