Re: PING: two middle-end builtin cproj patches

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Sun, 25 Apr 2010, Kaveh R. Ghazi wrote:
> and here is the update to the webpage:

This looks good from what I can tell.  Minor comments below:

> Index: changes.html
> ===================================================================
> +    <li>Versions of the GNU C library up to and including 2.11.1
> +    included an <a
> +    href="http://sourceware.org/bugzilla/show_bug.cgi?id=10401";>incorrect
> +    implementation of the <code>cproj</code> function</a>.  GCC

Have you considered saying "provided a" to avoid the double use of 
"include"?

> +    optimizes its builtin <code>cproj</code> according to the behavior
> +    specified and allowed by the ISO C99 standard.  If you want to
> +    avoid discrepancies between the C library and GCC's builtin
> +    transformations when using <code>cproj</code> in your code, use
> +    GLIBC 2.12 or later.

When used as an adjective, http://gcc.gnu.org/codingconventions.html
indicates that we shall use "built-in" (with a dash).

And how about "between the GNU C library..., use version 2.12 or later"?
This avoids "GLIBC" (which is not so standard, the project itselfs seems
to use glibc more often) and makes it yet more clear that if someone is
using a different libc she doesn't need to be concerned.

Gerald