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, fjh at cs dot mu dot oz dot au
- Subject: Re: forcing tail/sibling call optimization
- From: dewar at gnat dot com (Robert Dewar)
- Date: Sun, 26 Nov 2000 18:46:19 -0500 (EST)
- Cc: bernds at redhat dot com, gcc at gcc dot gnu dot org
Note that if you want to make a warning message a formal requirement,
then you must provide a formal definition of what a warning message is,
and I do not think you want to get into that sort of thing :-)
I think there is real merit in providing fairly formal specifications
for GNU C enhancements for three reasons.
1. The attempt to produce a FFS can often reveal difficulties that are
not apparent in a less formal approach.
2. If other C compilers want to copy the feature, which I assume we
welcome, then there is a clear guide.
3. If the ISO committee wants to copy the feature, which I assume
we welcome, then there is a clear guide.