public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60114] Incorrect column number for -pedantic and -Wconversion Date: Sat, 08 Feb 2014 16:21:00 -0000 [thread overview] Message-ID: <bug-60114-4-7ZtVfcBDsp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60114-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60114 --- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #4) > (In reply to Chengnian Sun from comment #2) > > It seems -pedantic and -Woverflow are different. When I issue > > $ gcc-trunk -c -Woverflow s.c > > then there is no overflow warning. (There is indeed no overflow.) > > > > But when I use > > $ gcc-trunk -c -pedantic s.c > > the warning says that it is emitted from -Woverflow. Is this expected? > > There are some warnings that are only enabled if -Wpedantic is given in > combination with other flag. Unfortunately, there is currently no way to say > that a warning is enabled by the combination of two flags, short of creating > a new flag -Wpedantic-overflow, which is enabled by the combination of > -Wpedantic && -Woverflow. I think it could be a nice workaround That said, I think it would be even nicer to print the flags that appear in the command-line (or pragmas) that triggered this warning, instead of the flag that controls it. So here it will print [-Wpedantic,-Woverflow]. Although we now record the relations between the flags explicitly in the *.opt files, there is no explicit structure that allows following the chain of dependencies. >From gcc-bugs-return-443055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 08 16:23:24 2014 Return-Path: <gcc-bugs-return-443055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 10863 invoked by alias); 8 Feb 2014 16:23:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 10594 invoked by uid 55); 8 Feb 2014 16:23:19 -0000 From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60066] Bad elemental invocation of non-scalar base object Date: Sat, 08 Feb 2014 16:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pault at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-60066-4-WHmzFYARxE@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60066-4@http.gcc.gnu.org/bugzilla/> References: <bug-60066-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg00812.txt.bz2 Content-length: 538 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`066 --- Comment #11 from Paul Thomas <pault at gcc dot gnu.org> --- Author: pault Date: Sat Feb 8 16:22:46 2014 New Revision: 207633 URL: http://gcc.gnu.org/viewcvs?rev 7633&root=gcc&view=rev Log: 2014-02-08 Paul Thomas <pault@gcc.gnu.org> PR fortran/60066 * gfortran.dg/elemental_subroutine_10.f90 : New test. This PR was fixed by the patch for PR59906. Added: trunk/gcc/testsuite/gfortran.dg/elemental_subroutine_10.f90 Modified: trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-02-08 16:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-08 2:08 [Bug c/60114] New: " chengniansun at gmail dot com 2014-02-08 8:08 ` [Bug c/60114] " mpolacek at gcc dot gnu.org 2014-02-08 8:36 ` chengniansun at gmail dot com 2014-02-08 8:50 ` mpolacek at gcc dot gnu.org 2014-02-08 16:09 ` manu at gcc dot gnu.org 2014-02-08 16:21 ` manu at gcc dot gnu.org [this message] 2014-02-10 17:50 ` mpolacek at gcc dot gnu.org 2014-02-10 17:50 ` mpolacek at gcc dot gnu.org 2014-04-25 10:50 ` mpolacek at gcc dot gnu.org 2014-04-25 10:52 ` mpolacek at gcc dot gnu.org 2014-07-16 20:15 ` yroux at gcc dot gnu.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=bug-60114-4-7ZtVfcBDsp@http.gcc.gnu.org/bugzilla/ \ --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).