From: Per Bothner <per@bothner.com>
To: Bernd Schmidt <bernds@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Is this a gcc bug?
Date: Thu, 11 Jan 2001 08:40:00 -0000 [thread overview]
Message-ID: <m2wvc2rqbk.fsf@kelso.bothner.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101111405550.1327-100000@host140.cambridge.redhat.com>
On Thu, 11 Jan 2001 dewar@gnat.com wrote:
> it seems like it would not be hard to implement a warning for the case where
> a variable is incremented or decremented somewhere in a statement, and
> referenced elsewhere
Bernd Schmidt <bernds@redhat.com> writes:
> Already there. You just have to turn on warnings.
>
> $ ./cc1 bug.i -Wall
> main
> bug.i: In function `main':
> bug.i:8: warning: operation on `x' may be undefined
I must say this is a very confusing error message, especally to
someone who does is not aware of the problem. I'm not sure I could
even begin to guess what it meant!
How about something like:
warning: 'x' may have unexpected value because of side-effects
or
warning: side-effects make value of 'x' undefined
or
warning: undefined order of side-effects on 'x'
One might replace "side-effects" by "updates" or "changes to".
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~2001-01-11 8:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 5:53 dewar
2001-01-11 6:06 ` Bernd Schmidt
2001-01-11 8:40 ` Per Bothner [this message]
2001-01-11 9:03 ` Richard Earnshaw
2001-01-11 9:27 ` Alexandre Oliva
2001-01-11 9:33 ` Joe Buck
2001-01-11 9:38 ` Bernd Schmidt
2001-01-11 9:44 ` Richard Earnshaw
2001-01-11 10:57 ` Neil Booth
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 13:01 Is this a GCC bug? Bingfeng Mei
2008-06-16 13:33 ` Bingfeng Mei
2001-01-17 23:30 Is this a gcc bug? Axel Kittenberger
2001-01-16 17:06 dewar
2001-01-14 16:14 dewar
2001-01-14 16:53 ` Dave Korn
2001-01-14 5:31 dewar
2001-01-14 15:51 ` Geoff Keating
2001-01-12 19:15 dewar
2001-01-12 19:29 ` Fergus Henderson
2001-01-12 19:14 dewar
2001-01-12 19:36 ` Alexandre Oliva
2001-01-12 18:21 dewar
2001-01-12 18:29 ` Joseph S. Myers
2001-01-12 18:49 ` Alexandre Oliva
2001-01-12 18:58 ` Fergus Henderson
2001-01-13 10:34 ` James Dennett
2001-01-16 17:01 ` Michael Eager
2001-01-17 3:21 ` Falk Hueffner
2001-01-17 14:57 ` Michael Eager
2001-01-12 1:18 Axel Kittenberger
2001-01-12 18:14 ` Alexandre Oliva
2001-01-12 19:11 ` Fergus Henderson
2001-01-13 3:21 ` Richard Earnshaw
2001-01-11 10:38 dewar
2001-01-11 10:30 dewar
2001-01-11 10:05 dewar
2001-01-11 10:00 David Korn
2001-01-11 21:36 ` Andy Walker
2001-01-13 18:45 ` Joern Rennecke
2001-01-14 2:21 ` Geoff Keating
2001-01-11 7:07 dewar
2001-01-11 5:49 dewar
2001-01-11 3:04 David Korn
2001-01-11 2:11 Uros Bizjak
2001-01-11 3:04 ` Alexandre Oliva
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=m2wvc2rqbk.fsf@kelso.bothner.com \
--to=per@bothner.com \
--cc=bernds@redhat.com \
--cc=gcc@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).