public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29582] Parameter pushed to stack too soon
Date: Tue, 31 Oct 2006 00:01:00 -0000 [thread overview]
Message-ID: <20061031000116.32498.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29582-12742@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from bangerth at dealii dot org 2006-10-31 00:01 -------
(In reply to comment #0)
> COtherClass(5, m_szSzField, NULL, 0,
> "ImmString1").Method1().Method2(m_ullProblemField)("ImmString2",
> m_pvPointerField)("ImmString3", m_ullProblemField);
> [...]
> The problem is that the value of m_ullProblemField is pushed to stack at the
> very beginning of code while it is modified later during invocation of
> COtherClass::Method2. COtherClass::operator (const char *, unsigned long long)
> should receive modified value of field but it receives initial one.
No. The order of evaluation of your sequence of function calls is
unspecified. There is no sequence point within your chain of calls, and
therefore the compiler is free to select whatever order for evaluating
the arguments of all these calls.
W.
--
bangerth at dealii dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bangerth at dealii dot org
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29582
prev parent reply other threads:[~2006-10-31 0:01 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
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 [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=20061031000116.32498.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).