From: John Love-Jensen <eljay@adobe.com>
To: Daniel Kabs <daniel.kabs@gmx.de>, MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: gcc not warning on all occurences of operations with undefined results?
Date: Tue, 15 Nov 2005 16:03:00 -0000 [thread overview]
Message-ID: <BF9F62C8.4E72%eljay@adobe.com> (raw)
In-Reply-To: <200511151448.24848.daniel.kabs@gmx.de>
Hi Daniel,
> IMHO, these lines also infringe upon the above mentioned rule or did I miss
> something important?
The compiler *CAN* warn about those kinds of infringements.
The compiler does *NOT* *HAVE* to warn about those kinds of infringements.
GCC 3.3.5 detects the simple case. It does not (I presume) detect the
indirect case that you provided.
In some situations it may be very hard to detect the indirect case during
compile time, and it could be very expensive to check for it at run time.
HTH,
--Eljay
next prev parent reply other threads:[~2005-11-15 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 13:48 Daniel Kabs
2005-11-15 16:03 ` John Love-Jensen [this message]
2005-11-15 20:33 ` Ladislav Mecir
2005-11-16 11:13 ` Daniel Kabs
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=BF9F62C8.4E72%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=daniel.kabs@gmx.de \
--cc=gcc-help@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).