Re: Integers and standard
- From: kargl@xxxxxxxxxxxxxxxxxxxxxxxxxxxx (Steven G. Kargl)
- Date: Tue, 29 Jul 2008 00:39:39 +0000 (UTC)
In article <Xktjk.138710$102.1217@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"James Giles" <jamesgiles@xxxxxxxxxxxxxxxx> writes:
Steven G. Kargl wrote:
In article
<02tjk.138695$102.39915@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "James
Giles" <jamesgiles@xxxxxxxxxxxxxxxx> writes:
I certainly think that if the compiler doesn't detect integer
overflow at run-time, there should at least be an option to
ignore the problem at compile-time as well.
-fno-range-check has been availabe for more than 2 years. RTFM.
I see no reason for foul language (unless the F in the above
abbreviationis to be assumed to be other than the usual). I already
stated quite clearly that I don't have gfortran installed. I don't
have the "fine" manual. I don't plan to get it. I was making
a statement about implementations in general. Your's happened
to be the specific one exemplified in the current thread.
You asked specific questions about gfortran, but in seeing
your response to Richard it is clear that these were rhetorical
questions so that you could have your BINGO! moment.
You can read the manual at
http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/
--
Steve
http://troutmask.apl.washington.edu/~kargl/
.
- References:
- Integers and standard
- From: Alfredo Buttari
- Re: Integers and standard
- From: Richard Maine
- Re: Integers and standard
- From: glen herrmannsfeldt
- Re: Integers and standard
- From: Steven G. Kargl
- Re: Integers and standard
- From: James Giles
- Re: Integers and standard
- From: Richard Maine
- Re: Integers and standard
- From: James Giles
- Re: Integers and standard
- From: Steven G. Kargl
- Re: Integers and standard
- From: James Giles
- Integers and standard
- Prev by Date: Re: Integers and standard
- Next by Date: Re: Integers and standard
- Previous by thread: Re: Integers and standard
- Next by thread: Re: Integers and standard
- Index(es):