From: dominiq@lps.ens.fr (Dominique Dhumieres)
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com,
joost.vandevondele@mat.ethz.ch
Subject: Re: [PATCH, Fortran] PR61234: -Wuse-no-only
Date: Sun, 01 Jun 2014 09:07:00 -0000 [thread overview]
Message-ID: <20140601090747.742D4105@mailhost.lps.ens.fr> (raw)
> I think it is really weird if a coding style warning is included in -Wall.
I fully agree. In top of that the patch looks like a blind enforcement of this
coding style.
What is the rationale of
+ SUBROUTINE S2
+ USE foo, ONLY: bar ! { dg-bogus "has no ONLY qualifier" }
+ END SUBROUTINE
?
Cheers,
Dominique
next reply other threads:[~2014-06-01 9:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 9:07 Dominique Dhumieres [this message]
2014-06-02 5:48 ` VandeVondele Joost
2014-06-10 10:09 ` Dominique Dhumieres
2014-07-30 14:24 ` VandeVondele Joost
-- 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=20140601090747.742D4105@mailhost.lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joost.vandevondele@mat.ethz.ch \
/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).