public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mueller at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11224] [3.3/3.4 regression] warning "value computed is not used" no longer emitted
Date: Wed, 18 Jun 2003 18:27:00 -0000	[thread overview]
Message-ID: <20030618182634.22394.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030617175603.11224.mueller@kde.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11224



------- Additional Comments From mueller at kde dot org  2003-06-18 18:26 -------
adding __attribute__ ((pure)) or __attribute__ ((const)) makes no difference.  
 
however, its indeed caused by the HAS_SIDEEFFECTS check, as further checking 
has confirmed.


  parent reply	other threads:[~2003-06-18 18:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17 17:56 [Bug c++/11224] New: [regression] " mueller@kde.org
2003-06-17 17:56 ` [Bug c++/11224] " mueller@kde.org
2003-06-17 18:12 ` [Bug c++/11224] [3.3/3.4 regression] " pinskia@physics.uc.edu
2003-06-17 18:26 ` dhazeghi@yahoo.com
2003-06-18 18:27 ` mueller at kde dot org [this message]
2003-06-27 21:45 ` mmitchel at gcc dot gnu dot org
2003-09-06 19:39 ` nathan at gcc dot gnu dot org
2003-12-29 17:51 ` pinskia at gcc dot gnu dot org
2004-01-10 23:22 ` pinskia at gcc dot gnu dot org
2004-01-12 23:39 ` steven at gcc dot gnu dot org
2004-02-20  9:09 ` [Bug c++/11224] [3.3/3.4/3.5 " mmitchel at gcc dot gnu dot org
2004-11-29 12:03 ` [Bug c++/11224] [3.3/3.4/4.0 " nathan at gcc dot gnu dot org
2004-12-22  4:57 ` mmitchel at gcc dot gnu dot org
2004-12-22 18:01 ` cvs-commit at gcc dot gnu dot org
2004-12-22 18:07 ` [Bug c++/11224] [3.3/3.4 " mmitchel at gcc dot gnu dot org
2005-01-10 19:01 ` jgrimm2 at us dot ibm dot com
2005-01-31  6:56 ` pinskia at gcc dot gnu dot org
2005-05-19 17:23 ` 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=20030618182634.22394.qmail@sources.redhat.com \
    --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).