From: Ian Lance Taylor <iant@google.com>
To: sankar chebolu <chnabsankar@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Variant code generation
Date: Wed, 16 Feb 2011 08:53:00 -0000 [thread overview]
Message-ID: <mcrzkpw31aj.fsf@google.com> (raw)
In-Reply-To: <90570.60405.qm@web30708.mail.mud.yahoo.com> (sankar chebolu's message of "Tue, 15 Feb 2011 21:25:05 -0800 (PST)")
sankar chebolu <chnabsankar@yahoo.com> writes:
> Does GCC has any command line switches which generate variant code?
> To be more precise, Does GCC has some switches which, if applied to certain input program, it is not necessary that they will generate exactly the same code everytime.
GCC is generally intended to be deterministic, in the sense that if you
run it twice with the same input and the same options, you should get
precisely the same result.
There are a few exceptions: there are a few places where GCC uses random
numbers. For those places you can use the -frandom-seed option where
deterministic output is important. See the description of that option
for the cases where random numbers are used.
Ian
prev parent reply other threads:[~2011-02-16 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297727993.9081.ezmlm@gcc.gnu.org>
2011-02-16 7:07 ` sankar chebolu
2011-02-16 8:53 ` Ian Lance Taylor [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=mcrzkpw31aj.fsf@google.com \
--to=iant@google.com \
--cc=chnabsankar@yahoo.com \
--cc=gcc-help@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).