From: "Dave Korn" <dave.korn@artimi.com>
To: "'Dave Korn'" <dave.korn@artimi.com>,
"'Mark Mendell'" <mendell@ca.ibm.com>,
"'Mark Mitchell'" <mark@codesourcery.com>
Cc: <Andrew_Pinski@playstation.sony.com>, "'gcc'" <gcc@gcc.gnu.org>,
"'Hans-Peter Nilsson'" <hp@bitrange.com>,
"'Richard Guenther'" <richard.guenther@gmail.com>,
<Russell_Olsen@playstation.sony.com>,
<trevor_smigiel@playstation.sony.com>
Subject: RE: __builtin_expect for indirect function calls
Date: Tue, 08 Jan 2008 15:51:00 -0000 [thread overview]
Message-ID: <003b01c8520e$45b7c3b0$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <003601c8520c$278d8390$2e08a8c0@CAM.ARTIMI.COM>
On 08 January 2008 15:36, Dave Korn wrote:
> On 07 January 2008 21:15, Mark Mendell wrote:
>
>> A question was raised: Are side effects in the second parameter guaranteed
>> to be executed? Is it valid for a compiler to ignore any side effects?
>
> That perked up my curiosity:
>
> " The value of C must be a compile-time constant. "
>
> Can a compile-time constant have run-time side-effects? I couldn't think
> up an example off the top of my head...
Ah, I thought of one, nevermind, sorry for the noise...
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2008-01-08 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 0:52 trevor_smigiel
2007-12-18 2:27 ` Jonathan Adamczewski
2007-12-22 3:42 ` Hans-Peter Nilsson
2007-12-26 19:10 ` Mark Mitchell
2008-01-03 23:36 ` trevor_smigiel
2008-01-05 5:44 ` Mark Mitchell
2008-01-05 10:40 ` Richard Guenther
2008-01-06 19:44 ` Mark Mitchell
2008-01-07 21:15 ` Mark Mendell
2008-01-08 15:36 ` Dave Korn
2008-01-08 15:51 ` Dave Korn [this message]
2008-01-03 23:46 ` trevor_smigiel
2008-01-06 20:42 Ross Ridge
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='003b01c8520e$45b7c3b0$2e08a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=Andrew_Pinski@playstation.sony.com \
--cc=Russell_Olsen@playstation.sony.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=mark@codesourcery.com \
--cc=mendell@ca.ibm.com \
--cc=richard.guenther@gmail.com \
--cc=trevor_smigiel@playstation.sony.com \
/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).