public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42809] Too much noise with -Wconversion Date: Mon, 10 May 2010 17:12:00 -0000 [thread overview] Message-ID: <20100510171134.26396.qmail@sourceware.org> (raw) In-Reply-To: <bug-42809-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from dfranke at gcc dot gnu dot org 2010-05-10 17:11 ------- Subject: Bug 42809 Author: dfranke Date: Mon May 10 17:10:53 2010 New Revision: 159238 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159238 Log: gcc/fortran/: 2010-05-10 Daniel Franke <franke.daniel@gmail.com> PR fortran/27866 PR fortran/35003 PR fortran/42809 * intrinsic.c (gfc_convert_type_warn): Be more discriminative about conversion warnings. gcc/testsuite/: 2010-05-08 Daniel Franke <franke.daniel@gmail.com> PR fortran/27866 PR fortran/35003 PR fortran/42809 * gfortran.dg/array_constructor_type_17.f03: Updated match string. * gfortran.dg/warn_conversion.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/warn_conversion.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/intrinsic.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/array_constructor_type_17.f03 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42809
next prev parent reply other threads:[~2010-05-10 17:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-19 22:39 [Bug fortran/42809] New: " anlauf at gmx dot de 2010-01-19 22:42 ` [Bug fortran/42809] " pinskia at gcc dot gnu dot org 2010-01-19 22:59 ` anlauf at gmx dot de 2010-01-20 23:02 ` anlauf at gmx dot de 2010-01-21 21:12 ` anlauf at gmx dot de 2010-01-22 20:43 ` anlauf at gmx dot de 2010-05-08 17:29 ` dfranke at gcc dot gnu dot org 2010-05-10 17:12 ` dfranke at gcc dot gnu dot org [this message] 2010-05-10 19:26 ` dfranke at gcc dot gnu dot org
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=20100510171134.26396.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).