From: Stephan Gatzka <stephan.gatzka@gmail.com>
To: Martin Sebor <msebor@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: parameter type of -frandom-seed
Date: Thu, 27 Aug 2015 05:36:00 -0000 [thread overview]
Message-ID: <1440653742.3277.11.camel@gmail.com> (raw)
In-Reply-To: <55DCFD7A.3090609@gmail.com>
Thanks for the answer.
> but it looks like there's a bug in the option's specification that
> prevents invalid (non-numeric) arguments from being diagnosed, making
> GCC accept anything (including negative numbers).
>
True, it accept strings and negative decimal numbers and hexadecimal
numbers and even gives me identical binaries...
So you would say that the only valid parameter to -frandom-seed is an
unsigned decimal number?
-frandom-seed=18464 // correct
-frandom-seed=a48cb9 //wrong
-frandom-seed=foobar //wrong
Regards,
Stephan
next prev parent reply other threads:[~2015-08-27 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 16:48 Stephan Gatzka
2015-08-25 23:42 ` Martin Sebor
2015-08-27 5:36 ` Stephan Gatzka [this message]
2015-08-27 15:31 ` Martin Sebor
2015-08-27 18:16 ` Stephan Gatzka
2015-09-01 17:33 ` Martin Sebor
2015-09-01 18:31 ` Stephan Gatzka
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=1440653742.3277.11.camel@gmail.com \
--to=stephan.gatzka@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=msebor@gmail.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).