public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26632] [4.1/4.2 Regression] spurious warning: value computed is not used
Date: Sun, 16 Apr 2006 18:58:00 -0000 [thread overview]
Message-ID: <20060416185830.29408.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26632-153@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from mmitchel at gcc dot gnu dot org 2006-04-16 18:58 -------
I am glad that Neil agrees my oft-stated, but always-rejected, claim that only
the front ends should issue warnings. :-)
However, in this case, we can presumably fix the bug by setting TREE_NO_WARNING
on the cast expression, which, one hopes, is generated by the front end.
In any case, this is definitely a bug.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26632
next prev parent reply other threads:[~2006-04-16 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 15:15 [Bug c/26632] New: " mattias at virtutech dot se
2006-03-10 15:17 ` [Bug middle-end/26632] " pinskia at gcc dot gnu dot org
2006-03-10 15:17 ` [Bug middle-end/26632] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-03-10 15:30 ` mattias at virtutech dot se
2006-03-11 0:16 ` neil at daikokuya dot co dot uk
2006-04-16 18:58 ` mmitchel at gcc dot gnu dot org [this message]
2006-05-25 2:46 ` mmitchel at gcc dot gnu dot org
2006-05-30 13:54 ` pinskia at gcc dot gnu dot org
2006-06-30 6:08 ` pinskia at gcc dot gnu dot org
2006-08-28 6:49 ` pinskia at gcc dot gnu dot org
2006-08-28 17:18 ` kazu at gcc dot gnu dot org
2006-08-30 6:00 ` [Bug middle-end/26632] [4.1 " kazu at gcc dot gnu dot org
2007-02-14 9:10 ` mmitchel at gcc dot gnu dot org
2008-07-04 15:23 ` jsm28 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=20060416185830.29408.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).