From: Erik Schnetter <schnetter@uni-tuebingen.de>
To: gcc@gcc.gnu.org
Subject: Re: restrict keyword [was: expalin this syntax pls]
Date: Sat, 19 Oct 2002 10:17:00 -0000 [thread overview]
Message-ID: <182oNW-0qRfKSC@fmrl00.sul.t-online.com> (raw)
You can't issue a hard error for it anyway, since the code might never
be executed. The key questions for issuing a warning (under its own
option, possibly included in -Wall) are:
* Can working code wrongly triggering the warning be easily changed,
even if automatically generated, so as not to trigger it? (The
relevant question for -Wall inclusion.)
If I had to translate a Fortran procedure to C, I would very likely
declare all arguments as restricted pointers. I think that the
definition of "restrict" in C and of non-aliasing in Fortran are close
enough to make that worthwhile. This would not be possible if "-Wall"
included a warning for passing the same pointer several times to a
procedure.
There might also an updated version of "f2c" be written at some time.
-erik
--
Erik Schnetter <schnetter@uni-tuebingen.de>
next reply other threads:[~2002-10-19 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 10:17 Erik Schnetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 4:23 expalin this syntax pls Jim Wilson
2002-10-18 14:27 ` restrict keyword [was: expalin this syntax pls] Joe Buck
2002-10-18 18:46 ` Joseph S. Myers
2002-10-18 21:53 ` Joe Buck
2002-10-18 21:55 ` Joseph S. Myers
2002-10-18 23:07 ` kwall
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=182oNW-0qRfKSC@fmrl00.sul.t-online.com \
--to=schnetter@uni-tuebingen.de \
--cc=gcc@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).