public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23563] [4.0 Regression] False warning for uninitialized variable: regression from 3.4.2
Date: Thu, 25 Aug 2005 17:58:00 -0000 [thread overview]
Message-ID: <20050825174856.26091.qmail@sourceware.org> (raw)
In-Reply-To: <20050825172028.23563.lennox@cs.columbia.edu>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-25 17:48 -------
Well I right in saying this is due to exceptions but is wrong in saying I can reproduce this on the
mainline.
It more has to do with not copying of the finally block (for the call of the deconstructor of stack_obj).
In 3.4.0 we copied the finally block in 4.0.2 we don't but in 4.1.0 we do again.
At -O2 we copy the finally block too.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |minor
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
GCC build triplet|i386-portbld-freebsd5.4 |
GCC host triplet|i386-portbld-freebsd5.4 |
GCC target triplet|i386-portbld-freebsd5.4 |
Keywords| |diagnostic, missed-
| |optimization
Last reconfirmed|0000-00-00 00:00:00 |2005-08-25 17:48:53
date| |
Summary|False warning for |[4.0 Regression] False
|uninitialized variable: |warning for uninitialized
|regression from 3.4.2 |variable: regression from
| |3.4.2
Target Milestone|--- |4.0.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23563
next prev parent reply other threads:[~2005-08-25 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 17:22 [Bug tree-optimization/23563] New: " lennox at cs dot columbia dot edu
2005-08-25 17:38 ` [Bug tree-optimization/23563] " lennox at cs dot columbia dot edu
2005-08-25 17:49 ` pinskia at gcc dot gnu dot org
2005-08-25 17:58 ` pinskia at gcc dot gnu dot org [this message]
2005-09-27 16:13 ` [Bug tree-optimization/23563] [4.0 Regression] " mmitchel 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=20050825174856.26091.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: 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).