public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17506] [4.0 regression] warning about uninitialized variable points to wrong location
Date: Thu, 16 Sep 2004 14:33:00 -0000 [thread overview]
Message-ID: <20040916143327.8954.qmail@sourceware.org> (raw)
In-Reply-To: <20040915183811.17506.nathan@gcc.gnu.org>
------- Additional Comments From nathan at gcc dot gnu dot org 2004-09-16 14:33 -------
No, I don't consider it a reasonable stopgap either :) Just thought I'd mention
it, if you find yourself in the same position. BTW, if you replace 'inline' with
'static' in the reduced testcase of #4, you'll get the same problem (which is
what happens in class.c). This is extremely confusing, because there are no
inline keywords anywhere :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17506
next prev parent reply other threads:[~2004-09-16 14:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 18:38 [Bug tree-optimization/17506] New: incorrect warning about non-existant variable nathan at gcc dot gnu dot org
2004-09-15 18:41 ` [Bug tree-optimization/17506] " nathan at gcc dot gnu dot org
2004-09-15 20:25 ` bangerth at dealii dot org
2004-09-15 20:27 ` bangerth at dealii dot org
2004-09-15 20:28 ` reichelt at gcc dot gnu dot org
2004-09-15 20:42 ` [Bug tree-optimization/17506] [4.0 regression] " nathan at gcc dot gnu dot org
2004-09-15 20:52 ` bangerth at dealii dot org
2004-09-15 21:37 ` [Bug tree-optimization/17506] [4.0 regression] warning about does say which variable is used as uninitialized pinskia at gcc dot gnu dot org
2004-09-15 22:17 ` [Bug tree-optimization/17506] [4.0 regression] warning about uninitialized variable points to wrong location bangerth at dealii dot org
2004-09-16 6:52 ` nathan at gcc dot gnu dot org
2004-09-16 12:49 ` bangerth at dealii dot org
2004-09-16 14:33 ` nathan at gcc dot gnu dot org [this message]
2004-10-21 4:06 ` pinskia at gcc dot gnu dot org
2004-10-21 4:09 ` pinskia at gcc dot gnu dot org
2004-11-25 20:57 ` pinskia at gcc dot gnu dot org
2005-01-20 23:52 ` reichelt at gcc dot gnu dot org
2005-04-21 5:05 ` [Bug tree-optimization/17506] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-08 1:41 ` mmitchel at gcc dot gnu dot org
2005-07-13 11:41 ` reichelt at gcc dot gnu dot org
2005-07-13 11:51 ` pinskia at gcc dot gnu dot org
2005-07-13 12:08 ` reichelt at gcc dot gnu dot org
2005-08-22 12:19 ` pinskia at gcc dot gnu dot org
2005-09-27 16:10 ` 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=20040916143327.8954.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).