public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc2eran at tromer dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21568] [4.0/4.1 regression] Casts in folding *& omitted
Date: Fri, 08 Jul 2005 09:18:00 -0000 [thread overview]
Message-ID: <20050708091839.10879.qmail@sourceware.org> (raw)
In-Reply-To: <20050514140942.21568.rguenth@gcc.gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
------- Additional Comments From gcc2eran at tromer dot org 2005-07-08 09:18 -------
(In reply to comment #13)
> In the C99 standard, 6.5.4 Cast Operators, Footnote 85 "A cast does not
> yield an lvalue. Thus, a cast to a qualified type has the same effect
> as a cast to the unqualified version of the type."
But the object being accessed is the one designated by *dereferencing* the cast
expression, and *that* is an lvalue. Quoting N1124:
"[6.5.3.2/4] The unary * operator denotes indirection. If the operand [...]
points to an object, the result is an lvalue designating the
object. If the operand has type pointer to type, the result has type
type."
And of course:
"[6.5.4/2] Preceding an expression by a parenthesized type name converts the
value of the expression to the named type. [...]"
I think this answers the first half of your quote (i.e., footnote 86), but I'm
not sure what to make of the second half, especially in light of the "Thus".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21568
prev parent reply other threads:[~2005-07-08 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 14:09 [Bug tree-optimization/21568] New: [3.4 " rguenth at gcc dot gnu dot org
2005-05-14 16:32 ` [Bug tree-optimization/21568] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-05-21 13:50 ` rguenth at gcc dot gnu dot org
2005-05-21 17:31 ` schlie at comcast dot net
2005-05-21 18:10 ` debian-gcc at lists dot debian dot org
2005-05-21 20:48 ` schlie at comcast dot net
2005-07-02 16:48 ` pinskia at gcc dot gnu dot org
2005-07-03 4:55 ` gcc2eran at tromer dot org
2005-07-03 5:52 ` pinskia at gcc dot gnu dot org
2005-07-03 6:50 ` gcc2eran at tromer dot org
2005-07-03 12:12 ` gcc2eran at tromer dot org
2005-07-03 17:33 ` schlie at comcast dot net
2005-07-06 18:42 ` gcc2eran at tromer dot org
2005-07-08 0:41 ` wilson at specifix dot com
2005-07-08 9:18 ` gcc2eran at tromer dot org [this message]
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=20050708091839.10879.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).