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/63272] GCC should warn when using pointer to dead scoped variable within the same function
Date: Tue, 16 Sep 2014 06:14:00 -0000 [thread overview]
Message-ID: <bug-63272-4-XAhktbrQRp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63272-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63272
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-09-16
CC| |manu at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
It would be nice to have. Perhaps related to PR49974.
>From gcc-bugs-return-461855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 16 06:38:12 2014
Return-Path: <gcc-bugs-return-461855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6177 invoked by alias); 16 Sep 2014 06:38:11 -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 6098 invoked by uid 48); 16 Sep 2014 06:38:00 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63272] GCC should warn when using pointer to dead scoped variable within the same function
Date: Tue, 16 Sep 2014 06:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-63272-4-u3bJmmcqAG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63272-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63272-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-09/txt/msg01689.txt.bz2
Content-length: 275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63272
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #1)
> It would be nice to have. Perhaps related to PR49974.
Definitely related to PR 53855.
>From gcc-bugs-return-461856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 16 06:40:09 2014
Return-Path: <gcc-bugs-return-461856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7532 invoked by alias); 16 Sep 2014 06:40:08 -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 7495 invoked by uid 48); 16 Sep 2014 06:40:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63272] GCC should warn when using pointer to dead scoped variable within the same function
Date: Tue, 16 Sep 2014 06:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-63272-4-lX1cLlDQ5e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63272-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63272-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/msg01690.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc272
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
But really this is already talked about the warning in bug 60517 and really in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id`770#c1 .
next prev parent reply other threads:[~2014-09-16 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 22:31 [Bug c/63272] New: " jacob.benoit.1 at gmail dot com
2014-09-16 6:14 ` manu at gcc dot gnu.org [this message]
2020-10-30 10:06 ` [Bug c/63272] " dcb314 at hotmail dot com
2021-11-01 22:21 ` msebor at gcc dot gnu.org
2021-12-16 23:31 ` msebor at gcc dot gnu.org
2021-12-17 9:06 ` [Bug middle-end/63272] " dcb314 at hotmail dot com
2022-01-15 23:46 ` cvs-commit at gcc dot gnu.org
2022-01-16 0:04 ` msebor at gcc dot gnu.org
2024-04-09 7:32 ` pinskia at gcc dot gnu.org
2024-04-09 7:33 ` pinskia 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-63272-4-XAhktbrQRp@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).