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/49859] gcc could warn about statements between "switch" and first "case"
Date: Tue, 23 Sep 2014 15:24:00 -0000	[thread overview]
Message-ID: <bug-49859-4-pgc2U2I9Uk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49859-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49859

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
For sure we do not need the old -Wunreachable here. Just when parsing a switch
block, anything found before the first case is basically unreachable, no?

(Why the standard does not consider this an error?)
>From gcc-bugs-return-462349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 23 15:26:33 2014
Return-Path: <gcc-bugs-return-462349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23265 invoked by alias); 23 Sep 2014 15:26:33 -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 23200 invoked by uid 55); 23 Sep 2014 15:26:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/63331] Fortran -fcompare-debug issues
Date: Tue, 23 Sep 2014 15:26: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: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-63331-4-UoO6rtAoO2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63331-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-09/txt/msg02183.txt.bz2
Content-length: 592

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc331

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Sep 23 15:25:55 2014
New Revision: 215516

URL: https://gcc.gnu.org/viewcvs?rev!5516&root=gcc&view=rev
Log:
    PR fortran/63331
    * trans-types.c (gfc_get_array_descr_info): Build DEBUG_EXPR_DECL
    instead of VAR_DECL for base_decl.

    * gfortran.dg/pr63331.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr63331.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-types.c
    trunk/gcc/testsuite/ChangeLog


      parent reply	other threads:[~2014-09-23 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  1:15 [Bug c/49859] New: " wkoszek at gmail dot com
2011-07-27  1:16 ` [Bug c/49859] " wkoszek at gmail dot com
2011-07-27  1:22 ` pinskia at gcc dot gnu.org
2011-07-27  1:28 ` wkoszek at gmail dot com
2011-07-27 10:07 ` rguenth at gcc dot gnu.org
2014-09-23 15:24 ` manu at gcc dot gnu.org [this message]

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-49859-4-pgc2U2I9Uk@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: 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).