From: law@redhat.com
To: gcc@gcc.gnu.org
Subject: Question for ISO C standards gurus
Date: Thu, 25 Mar 2004 18:47:00 -0000 [thread overview]
Message-ID: <200403251803.i2PI384m020124@speedy.slc.redhat.com> (raw)
Given something like this:
execfuncdef(Estate state, int do_exec)
{
Shfunc shf;
char *s;
int signum, nprg, sbeg, nstrs, npats, len, plen, i, htok = 0;
Wordcode beg = state->pc, end;
Eprog prog;
Patprog *pp;
LinkList names;
end = beg + ((state->pc[-1]) >> 5);
if (!(names = ecgetlist(state, *state->pc++, 2, &htok))) {
state->pc = end;
return 0;
}
}
Does the ISO standard say anything about when the side effect of incrementing
state->pc takes effect? Or is it implementation dependent? Of particular
interest is whether or not the increment occurs before the call or after
the call.
jeff
next reply other threads:[~2004-03-25 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 18:47 law [this message]
2004-03-25 18:58 ` Dave Korn
2004-03-27 1:35 ` Diego Novillo
2004-03-27 11:25 ` Ian Lance Taylor
2004-03-27 14:25 ` Diego Novillo
2004-03-29 17:18 ` Dave Korn
2004-03-27 21:56 ` law
2004-03-25 18:59 ` Paul Jarc
2004-03-25 19:14 ` Dale Johannesen
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=200403251803.i2PI384m020124@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=gcc@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).