This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH, rs6000] Clarify when typedef names can be used with AltiVec vector types
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Bill Schmidt <wschmidt at linux dot ibm dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, uweigand at de dot ibm dot com
- Date: Tue, 18 Dec 2018 03:13:07 -0600
- Subject: Re: [PATCH, rs6000] Clarify when typedef names can be used with AltiVec vector types
- References: <firstname.lastname@example.org>
On Mon, Dec 17, 2018 at 03:54:23PM -0600, Bill Schmidt wrote:
> We recently discovered some incorrect documentation about this topic and agreed it should be changed.
> This is my attempt to clarify it. Built and verified on powerpc64le-linux-gnu. Is this ok for trunk?
Okay for trunk and all backports you want. Thanks!
> 2018-12-17 Bill Schmidt <email@example.com>
> * doc/extend.texi (PowerPC Altivec/VSX Built-in Functions):
> Describe when a typedef name can be used as the type specifier for
> a vector type, and when it cannot.