public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oder at eleks dot lviv dot ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29582] Parameter pushed to stack too soon
Date: Tue, 24 Oct 2006 16:10:00 -0000 [thread overview]
Message-ID: <20061024160950.13571.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29582-12742@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from oder at eleks dot lviv dot ua 2006-10-24 16:09 -------
(In reply to comment #1)
> The evaluation order of function arguments is not specified. If you depend on
> side effects to be carried out at a specific point you must make sure there is
> a sequence point at the appropriate place.
These are not the arguments of a single function. Given example is the sequence
of method invocations for a class instance. Modification of lvalue occurs in
2nd method invocation and it is supposed to be passed to 4th method invocation.
--
oder at eleks dot lviv dot ua changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29582
next prev parent reply other threads:[~2006-10-24 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 15:56 [Bug c++/29582] New: " oder at eleks dot lviv dot ua
2006-10-24 16:03 ` [Bug c++/29582] " schwab at suse dot de
2006-10-24 16:10 ` oder at eleks dot lviv dot ua [this message]
2006-10-29 20:40 ` pinskia at gcc dot gnu dot org
2006-10-30 8:33 ` oder at eleks dot lviv dot ua
2006-10-30 8:41 ` oder at eleks dot lviv dot ua
2006-10-31 0:01 ` bangerth at dealii 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=20061024160950.13571.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).