This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: forcing tail/sibling call optimization
- To: dewar at gnat dot com (Robert Dewar)
- Subject: Re: forcing tail/sibling call optimization
- From: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Mon, 27 Nov 2000 08:51:40 +1100
- Cc: bernds at redhat dot com, gcc at gcc dot gnu dot org
- References: <20001126162142.14A3D34D83@nile.gnat.com>
On 26-Nov-2000, Robert Dewar <dewar@gnat.com> wrote:
> > Implementations shall issue a warning if there are any tail call
> > statements for which the implementation is unable to follow
> > the implementation advice.
>
> Are there precedents in either ANSI C or GNU C for requiring warnings.
In ANSI/ISO C: no. But the ANSI/ISO C standard is not a good model
for how to write specifications.
In GNU C: yes. For example, many parts of the GNU C manual say
that if a certain option is enabled, the compiler will issue
certain warnings. If the GNU C manual is treated as a specification,
these parts of the manual are definitely requirements on the compiler.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.