This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [wwwdocs] A few more 4.1 changes items


On Tue, 2 Aug 2005, Steven Bosscher wrote:
> This adds IPCP, fixes the grammar of another entry, and adds
> other finished projects mentioned on the 4.1 projects wiki page.
> Does this look OK?

I wonder whether we shouldn't make you a co-maintainer for the
gcc-X.Y/changes.html pages. :-)

Good stuff.

> Index: htdocs/gcc-4.1/changes.html
> ===================================================================
> +<h3>RS6000 (POWER/PowerPC)</h3>
> +  <ul>
> +    <li>The AltiVec vector primitives are now implemented in a way that puts
> +	a smaller burden on the preprocessor, instead processing the
> +	"overloading" in the C front-end.  This should benefit compilation
> +	speed on AltiVec vector code.</li>
> +  </ul>

Are these primitives also supported in the C/C++/Objective-C front ends?
(According to codedingconventions.html it's "front ends", not "frontends",
though I'll readily admit that I just had to check because I always forget.)

> +    <li>Some builtin functions have been fortified to protect them against
> +	various buffer overflow (and format string) vulnerabilities. Compared
> +	to the mudflap bounds checking feature, the safe builtins have far
> +	smaller overhead.  This means that programs built using safe builtins
> +	should not experiece any measurable slowdown.</li>
                       ^^^^
                       Typo

And "built-in" instead of "builtin".  (Yes, I had to look it up myself. ;-)

Thanks a bunch!

Gerald


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]