public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/43456] gcc -O code generation error
Date: Sat, 20 Mar 2010 21:54:00 -0000 [thread overview]
Message-ID: <20100320215427.10072.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43456-18943@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from pinskia at gcc dot gnu dot org 2010-03-20 21:54 -------
(In reply to comment #7)
> Subject: Re: gcc -O code generation error
>
> To clarify even further, we have
>
> (..., (f->sp++)->u.number [SEQUENCE POINT] ? 1 : 0) |
> (..., (f->sp++)->u.number [SEQUENCE POINT] ? 4 : 0)
>
> So the modifications of f->sp are before the sequence point. If
> gcc -W -Wall warns about this part of the expression, that warning is
> wrong, as well.
No, we have a | b. There is an order inside a and b but no order between a and
b.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43456
next prev parent reply other threads:[~2010-03-20 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 20:30 [Bug c/43456] New: " gccbug at dworkin dot nl
2010-03-20 20:40 ` [Bug c/43456] " pinskia at gcc dot gnu dot org
2010-03-20 20:53 ` rguenth at gcc dot gnu dot org
2010-03-20 20:59 ` pinskia at gcc dot gnu dot org
2010-03-20 21:01 ` rguenth at gcc dot gnu dot org
2010-03-20 21:17 ` pinskia at gcc dot gnu dot org
2010-03-20 21:18 ` pinskia at gcc dot gnu dot org
2010-03-20 21:51 ` gccbug at dworkin dot nl
2010-03-20 21:54 ` pinskia at gcc dot gnu dot org [this message]
2010-03-20 23:14 ` gccbug at dworkin dot nl
2010-03-20 23:19 ` pinskia at gcc dot gnu dot org
2010-03-20 23:46 ` joseph at codesourcery dot com
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=20100320215427.10072.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).