From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Richard Henderson <rth@redhat.com>
Cc: Robert Dewar <dewar@gnat.com>, alexr@spies.com, gcc@gcc.gnu.org
Subject: Re: [lno] [RFC] if-conversion and auto vectorizer
Date: Tue, 16 Mar 2004 22:51:00 -0000 [thread overview]
Message-ID: <405785FF.8040009@moene.indiv.nluug.nl> (raw)
In-Reply-To: <20040316183250.GA12315@redhat.com>
Richard Henderson wrote:
> For the same reasons that we preserve a set of rules that are
> beyond C89 such that it's possible to write kernels.
Ah, I already thought so [well, actually, I was thinking "embedded
systems"].
Can I have an option (to be set by default to "yes" by the various
Fortran front ends) that says:
No valid (Fortran) program can cause the generation of floating point
exceptions or memory access violations ?
Even Fortran 2003 will only allow 1.0/0.0 to cause a (legal) exception
if you first specify:
USE IEEE_EXCEPTIONS
and the (as yet hypothetical) front end implementing that Standard could
easily flip the switch on seeing that statement *for the translation unit*.
Thanks in advance,
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc.gnu.org/fortran/ (under construction)
next prev parent reply other threads:[~2004-03-16 22:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 12:27 Robert Dewar
2004-03-16 18:32 ` Richard Henderson
2004-03-16 22:51 ` Toon Moene [this message]
2004-03-16 23:10 ` Joseph S. Myers
2004-03-16 23:28 ` Toon Moene
2004-03-16 23:37 ` Richard Henderson
2004-03-16 23:42 ` Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 5:33 Robert Dewar
2004-03-16 6:54 ` Richard Henderson
2004-03-16 3:46 Chris Lattner
2004-03-15 22:42 Robert Dewar
2004-03-15 23:08 ` Richard Henderson
2004-03-14 10:57 Fw: " Dorit Naishlos
2004-03-14 19:22 ` Andrew Pinski
2004-03-14 22:31 ` Daniel Berlin
2004-03-15 2:29 ` Alex Rosenberg
2004-03-15 22:38 ` Richard Henderson
2004-03-15 23:08 ` Devang Patel
2004-03-15 23:20 ` Richard Henderson
2004-03-16 0:02 ` Devang Patel
2004-03-16 0:07 ` Diego Novillo
2004-03-16 0:45 ` Richard Henderson
2004-03-16 3:02 ` Diego Novillo
2004-03-16 3:33 ` Richard Henderson
2004-03-16 6:33 ` Devang Patel
2004-03-04 19:59 Devang Patel
2004-03-04 20:12 ` Andrew Pinski
2004-03-04 20:39 ` Devang Patel
2004-03-04 21:03 ` Richard Henderson
2004-03-05 19:06 ` Devang Patel
2004-03-05 19:17 ` Diego Novillo
2004-03-05 19:22 ` Diego Novillo
2004-03-05 19:28 ` Devang Patel
2004-03-05 19:41 ` Diego Novillo
2004-03-05 19:44 ` Diego Novillo
2004-03-12 18:45 ` Devang Patel
2004-03-13 9:24 ` Zdenek Dvorak
2004-03-13 22:41 ` Devang Patel
2004-03-14 10:59 ` Dorit Naishlos
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=405785FF.8040009@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=alexr@spies.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).