Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Bill Schmidt]

Fixed with r250952.

Bill

> On Aug 6, 2017, at 3:08 AM, Andreas Schwab  wrote:
> 
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c  (test for errors, line 
> 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c  (test for errors, line 
> 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c  (test for errors, line 
> 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c  (test for errors, line 
> 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c  (test for errors, line 
> 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c (test for excess errors)
> FAIL: gcc.target/powerpc/cmpb-3.c  (test for errors, line 12)
> FAIL: gcc.target/powerpc/cmpb-3.c (test for excess errors)
> FAIL: gcc.target/powerpc/byte-in-set-2.c  (test for errors, line 15)
> FAIL: gcc.target/powerpc/byte-in-set-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c  (test for errors, line 17)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c  (test for errors, line 18)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c (test for excess errors)
> 
> Andreas.
> 
> -- 
> Andreas Schwab, sch...@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
> 

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Segher Boessenkool]

Hi Andreas,

On Sun, Aug 06, 2017 at 10:08:23AM +0200, Andreas Schwab wrote:
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c  (test for errors, line 
> 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c  (test for errors, line 
> 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c  (test for errors, line 
> 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c  (test for errors, line 
> 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c  (test for errors, line 
> 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c  (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c (test for excess errors)
> FAIL: gcc.target/powerpc/cmpb-3.c  (test for errors, line 12)
> FAIL: gcc.target/powerpc/cmpb-3.c (test for excess errors)
> FAIL: gcc.target/powerpc/byte-in-set-2.c  (test for errors, line 15)
> FAIL: gcc.target/powerpc/byte-in-set-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c  (test for errors, line 17)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c  (test for errors, line 18)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c (test for excess errors)

What target?  What configure options?  What runtest options?  What
binutils version?  What is the actual CPU?

Or, do you have a link to a gcc-testresults post with that info?


Segher

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Andreas Schwab]

FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c  (test for errors, line 18)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c  (test for errors, line 18)
FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c  (test for errors, line 16)
FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c  (test for errors, line 16)
FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c  (test for errors, line 20)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c  (test for errors, line 20)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c  (test for errors, line 20)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c (test for excess errors)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c  (test for errors, line 20)
FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c (test for excess errors)
FAIL: gcc.target/powerpc/cmpb-3.c  (test for errors, line 12)
FAIL: gcc.target/powerpc/cmpb-3.c (test for excess errors)
FAIL: gcc.target/powerpc/byte-in-set-2.c  (test for errors, line 15)
FAIL: gcc.target/powerpc/byte-in-set-2.c (test for excess errors)
FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c  (test for errors, line 17)
FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c (test for excess errors)
FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c  (test for errors, line 18)
FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c (test for excess errors)

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Bill Schmidt]

> On Aug 2, 2017, at 6:43 PM, Segher Boessenkool  
> wrote:
> 
> Hi Bill,
> 
> On Wed, Aug 02, 2017 at 10:29:20AM -0500, Bill Schmidt wrote:
>> I don't anticipate backporting any of this.
> 
> Good :-)
> 
>> @@ -6802,7 +6802,7 @@ altivec_resolve_overloaded_builtin (location_t loc
>> if (unsupported_builtin)
>>   {
>>  const char *name = rs6000_overloaded_builtin_name (fcode);
>> -error ("Builtin function %s not supported in this compiler 
>> configuration",
>> +error ("builtin function %s not supported in this compiler 
>> configuration",
>> name);
> 
> As Martin says, %qs for this and similar (see the documentation before
> pp_format in pretty-print.c).  Can be a separate patch of course, this
> one is big enough already.
> 
>> Index: gcc/config/rs6000/rs6000.c
>> ===
>> --- gcc/config/rs6000/rs6000.c   (revision 250791)
>> +++ gcc/config/rs6000/rs6000.c   (working copy)
>> @@ -4132,7 +4132,7 @@ rs6000_option_override_internal (bool global_init_
>>   || rs6000_cpu == PROCESSOR_PPCE5500)
>> {
>>   if (TARGET_ALTIVEC)
>> -error ("AltiVec not supported in this target");
>> +error ("altivec not supported in this target");
>> }
>> 
>>   /* If we are optimizing big endian systems for space, use the load/store
> 
> Let's either keep AltiVec or say -maltivec.  We only have this warning
> because we allow -maltivec with CPUs that do not support it; and this
> warning is only for some of the FSL CPUs.  It isn't very consistent.

Back to AltiVec it goes!  Thanks.

> 
>> @@ -4250,7 +4250,7 @@ rs6000_option_override_internal (bool global_init_
>>rs6000_isa_flags |= (ISA_3_0_MASKS_SERVER & ~ignore_masks);
>>  }
>>else
>> -error ("Power9 target option is incompatible with -mcpu= for "
>> +error ("power9 target option is incompatible with -mcpu= for "
>> " less than power9");
>>  }
>>   else if ((ISA_3_0_MASKS_SERVER & rs6000_isa_flags_explicit)
> 
> See also PR79477.  Since many of these options are going away it is
> probably not worth spending too much time on this, not until stage 3
> or so anyway.

Yeah, let's address that later in the year after Mike finishes his cleanups.

> 
>> @@ -11226,7 +11226,7 @@ rs6000_return_in_memory (const_tree type, const_tr
>>   static bool warned_for_return_big_vectors = false;
>>   if (!warned_for_return_big_vectors)
>>  {
>> -  warning (OPT_Wpsabi, "GCC vector returned by reference: "
>> +  warning (OPT_Wpsabi, "gcc vector returned by reference: "
>> "non-standard ABI extension with no compatibility 
>> guarantee");
>>warned_for_return_big_vectors = true;
>>  }
> 
> Maybe the warning should just say "big vector"?  Or "generic vector"?
> 
> (Vectors that fit in one VR, or in GPRs in 8 bytes or less, do not have
> the problem this warns for.  Kind of hard to express tersely and
> precisely though).

I looked in the GCC manual and couldn't find a better way of expressing
this than just "GCC vector," so I will return it to the way it was.  "GCC 
vector extension vector" is accurate but hardly trips lightly off the
tongue...

> 
> Approved for trunk with whichever of the suggested changes you think
> are good.  Thanks,

Thanks much!

Bill

> 
> 
> Segher
> 

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Segher Boessenkool]

Hi Bill,

On Wed, Aug 02, 2017 at 10:29:20AM -0500, Bill Schmidt wrote:
> I don't anticipate backporting any of this.

Good :-)

> @@ -6802,7 +6802,7 @@ altivec_resolve_overloaded_builtin (location_t loc
>  if (unsupported_builtin)
>{
>   const char *name = rs6000_overloaded_builtin_name (fcode);
> - error ("Builtin function %s not supported in this compiler 
> configuration",
> + error ("builtin function %s not supported in this compiler 
> configuration",
>  name);

As Martin says, %qs for this and similar (see the documentation before
pp_format in pretty-print.c).  Can be a separate patch of course, this
one is big enough already.

> Index: gcc/config/rs6000/rs6000.c
> ===
> --- gcc/config/rs6000/rs6000.c(revision 250791)
> +++ gcc/config/rs6000/rs6000.c(working copy)
> @@ -4132,7 +4132,7 @@ rs6000_option_override_internal (bool global_init_
>|| rs6000_cpu == PROCESSOR_PPCE5500)
>  {
>if (TARGET_ALTIVEC)
> - error ("AltiVec not supported in this target");
> + error ("altivec not supported in this target");
>  }
>  
>/* If we are optimizing big endian systems for space, use the load/store

Let's either keep AltiVec or say -maltivec.  We only have this warning
because we allow -maltivec with CPUs that do not support it; and this
warning is only for some of the FSL CPUs.  It isn't very consistent.

> @@ -4250,7 +4250,7 @@ rs6000_option_override_internal (bool global_init_
> rs6000_isa_flags |= (ISA_3_0_MASKS_SERVER & ~ignore_masks);
>   }
> else
> - error ("Power9 target option is incompatible with -mcpu= for "
> + error ("power9 target option is incompatible with -mcpu= for "
>  " less than power9");
>   }
>else if ((ISA_3_0_MASKS_SERVER & rs6000_isa_flags_explicit)

See also PR79477.  Since many of these options are going away it is
probably not worth spending too much time on this, not until stage 3
or so anyway.

> @@ -11226,7 +11226,7 @@ rs6000_return_in_memory (const_tree type, const_tr
>static bool warned_for_return_big_vectors = false;
>if (!warned_for_return_big_vectors)
>   {
> -   warning (OPT_Wpsabi, "GCC vector returned by reference: "
> +   warning (OPT_Wpsabi, "gcc vector returned by reference: "
>  "non-standard ABI extension with no compatibility 
> guarantee");
> warned_for_return_big_vectors = true;
>   }

Maybe the warning should just say "big vector"?  Or "generic vector"?

(Vectors that fit in one VR, or in GPRs in 8 bytes or less, do not have
the problem this warns for.  Kind of hard to express tersely and
precisely though).

Approved for trunk with whichever of the suggested changes you think
are good.  Thanks,


Segher

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Bill Schmidt]

On Aug 2, 2017, at 11:04 AM, Joseph Myers  wrote:
> 
> On Wed, 2 Aug 2017, Jakub Jelinek wrote:
> 
>> On Wed, Aug 02, 2017 at 10:29:20AM -0500, Bill Schmidt wrote:
>>> --- gcc/config/rs6000/rs6000.c  (revision 250791)
>>> +++ gcc/config/rs6000/rs6000.c  (working copy)
>>> @@ -4132,7 +4132,7 @@ rs6000_option_override_internal (bool global_init_
>>>   || rs6000_cpu == PROCESSOR_PPCE5500)
>>> {
>>>   if (TARGET_ALTIVEC)
>>> -   error ("AltiVec not supported in this target");
>>> +   error ("altivec not supported in this target");
>> 
>> If AltiVec is spelled that way always, then I think we want to keep it
>> capitalized, but CCing Joseph just to be sure.  Or the diagnostics
> 
> Yes, if it would be capitalized mid-sentence then it should be capitalized 
> at the start of a diagnostic (and if it wouldn't be capitalized 
> mid-sentence, it shouldn't be capitalized at the start of a diagnostic).

Honestly, if I had my way we would retroactively change all the
"altivec/Altivec/AltiVec" inconsistencies to "VMX". ;-)  But given the
ubiquity of  (lowercase there) I suppose that's not practical...

I'll return this one to AltiVec, and change "GCC vector" to "GNU vector"
if that's okay with everyone.

Bill

> 
> -- 
> Joseph S. Myers
> jos...@codesourcery.com
> 

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Martin Sebor]

On 08/02/2017 09:29 AM, Bill Schmidt wrote:

Hi,

Jakub pointed out that we've had several error messages slip into the POWER 
back end
that incorrectly start with a capital letter.  This patch hunts those down and 
cleans
them up.


Others have already commented on some aspects of the patch but
let me suggest that using the option that controls it instead
of changing the spelling of AltiVec would bypass the whole
capitalization issue and might also provide an additional detail
that may otherwise not be immediately obvious.

Also, while making changes to the diagnostics, it would be great
to also add quoting around the built-in names and option names as
in:


--- gcc/config/rs6000/rs6000-c.c(revision 250791)
+++ gcc/config/rs6000/rs6000-c.c(working copy)
@@ -6802,7 +6802,7 @@ altivec_resolve_overloaded_builtin (location_t loc
 if (unsupported_builtin)
   {
const char *name = rs6000_overloaded_builtin_name (fcode);
-   error ("Builtin function %s not supported in this compiler 
configuration",
+   error ("builtin function %s not supported in this compiler 
configuration",


use %qs instead:

  error ("builtin function %qs not supported in this compiler 
configuration", ...);


and similarly here:


+   error ("power9 target option is incompatible with -mcpu= for "
   " less than power9");


Here too, I suggest to consider using and quoting an option that
enables the to power9 target rather than using power9 as a plain
word.

Martin

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Joseph Myers]

On Wed, 2 Aug 2017, Jakub Jelinek wrote:

> On Wed, Aug 02, 2017 at 10:29:20AM -0500, Bill Schmidt wrote:
> > --- gcc/config/rs6000/rs6000.c  (revision 250791)
> > +++ gcc/config/rs6000/rs6000.c  (working copy)
> > @@ -4132,7 +4132,7 @@ rs6000_option_override_internal (bool global_init_
> >|| rs6000_cpu == PROCESSOR_PPCE5500)
> >  {
> >if (TARGET_ALTIVEC)
> > -   error ("AltiVec not supported in this target");
> > +   error ("altivec not supported in this target");
> 
> If AltiVec is spelled that way always, then I think we want to keep it
> capitalized, but CCing Joseph just to be sure.  Or the diagnostics

Yes, if it would be capitalized mid-sentence then it should be capitalized 
at the start of a diagnostic (and if it wouldn't be capitalized 
mid-sentence, it shouldn't be capitalized at the start of a diagnostic).

-- 
Joseph S. Myers
jos...@codesourcery.com

Re: [PATCH, rs6000] Clean up capitalized diagnostic messages

[Jakub Jelinek]

On Wed, Aug 02, 2017 at 10:29:20AM -0500, Bill Schmidt wrote:
> --- gcc/config/rs6000/rs6000.c(revision 250791)
> +++ gcc/config/rs6000/rs6000.c(working copy)
> @@ -4132,7 +4132,7 @@ rs6000_option_override_internal (bool global_init_
>|| rs6000_cpu == PROCESSOR_PPCE5500)
>  {
>if (TARGET_ALTIVEC)
> - error ("AltiVec not supported in this target");
> + error ("altivec not supported in this target");

If AltiVec is spelled that way always, then I think we want to keep it
capitalized, but CCing Joseph just to be sure.  Or the diagnostics
could be reworded not to have AltiVec first.

> @@ -4250,7 +4250,7 @@ rs6000_option_override_internal (bool global_init_
> rs6000_isa_flags |= (ISA_3_0_MASKS_SERVER & ~ignore_masks);
>   }
> else
> - error ("Power9 target option is incompatible with -mcpu= for "
> + error ("power9 target option is incompatible with -mcpu= for "
>  " less than power9");
>   }
>else if ((ISA_3_0_MASKS_SERVER & rs6000_isa_flags_explicit)

Similarly, not sure about this one, but isn't it about -mpower9-minmax
being incompatible with -mcpu option not supporting power9 ISA?
The  and talking about less for strings that aren't necessarily ordered
is just weird.

> @@ -11226,7 +11226,7 @@ rs6000_return_in_memory (const_tree type, const_tr
>static bool warned_for_return_big_vectors = false;
>if (!warned_for_return_big_vectors)
>   {
> -   warning (OPT_Wpsabi, "GCC vector returned by reference: "
> +   warning (OPT_Wpsabi, "gcc vector returned by reference: "
>  "non-standard ABI extension with no compatibility 
> guarantee");
> warned_for_return_big_vectors = true;
>   }
> @@ -12773,7 +12773,7 @@ rs6000_pass_by_reference (cumulative_args_t cum AT
>   fprintf (stderr, "function_arg_pass_by_reference: synthetic vector\n");
>if (!warned_for_pass_big_vectors)
>   {
> -   warning (OPT_Wpsabi, "GCC vector passed by reference: "
> +   warning (OPT_Wpsabi, "gcc vector passed by reference: "
>  "non-standard ABI extension with no compatibility 
> guarantee");
> warned_for_pass_big_vectors = true;
>   }

GCC I think needs to be capitalized.  Not sure if talking about GCC vector
is clear, it is talking about the GNU vector extension, perhaps GNU instead?

The rest of the changes look good to me, but I'll defer review to the target
maintainers.

Jakub

[PATCH, rs6000] Clean up capitalized diagnostic messages

[Bill Schmidt]

Hi,

Jakub pointed out that we've had several error messages slip into the POWER 
back end
that incorrectly start with a capital letter.  This patch hunts those down and 
cleans
them up.

Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.  Is this 
ok for
trunk?  I don't anticipate backporting any of this.

Thanks,
Bill


[gcc]

2017-08-02  Bill Schmidt  

* config/rs6000/rs6000-c.c (altivec_resolve_overloaded_builtin):
Don't start diagnostic messages with a capital letter.
* config/rs6000/rs6000.c (rs6000_option_override_internal):
Likewise.
(rs6000_return_in_memory): Likewise.
(rs6000_pass_by_reference): Likewise.
(rs6000_invalid_builtin): Likewise.
(rs6000_trampoline_init): Likewise.

[gcc/testsuite]

2017-08-02  Bill Schmidt  

* gcc.dg/pr35442.c: Adjust for error messages that used to start
with a capital letter.
* gcc.target/powerpc/bfp/scalar-cmp-exp-eq-2.c: Likewise.
* gcc.target/powerpc/bfp/scalar-cmp-exp-gt-2.c: Likewise.
* gcc.target/powerpc/bfp/scalar-cmp-exp-lt-2.c: Likewise.
* gcc.target/powerpc/bfp/scalar-cmp-unordered-2.c: Likewise.
* gcc.target/powerpc/bfp/scalar-extract-exp-1.c: Likewise.
* gcc.target/powerpc/bfp/scalar-extract-exp-4.c: Likewise.
* gcc.target/powerpc/bfp/scalar-extract-sig-1.c: Likewise.
* gcc.target/powerpc/bfp/scalar-extract-sig-4.c: Likewise.
* gcc.target/powerpc/bfp/scalar-insert-exp-1.c: Likewise.
* gcc.target/powerpc/bfp/scalar-insert-exp-10.c: Likewise.
* gcc.target/powerpc/bfp/scalar-insert-exp-4.c: Likewise.
* gcc.target/powerpc/bfp/scalar-insert-exp-7.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-data-class-11.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-data-class-6.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-data-class-7.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-neg-2.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-neg-3.c: Likewise.
* gcc.target/powerpc/bfp/scalar-test-neg-5.c: Likewise.
* gcc.target/powerpc/bfp/vec-extract-exp-2.c: Likewise.
* gcc.target/powerpc/bfp/vec-extract-exp-3.c: Likewise.
* gcc.target/powerpc/bfp/vec-extract-sig-2.c: Likewise.
* gcc.target/powerpc/bfp/vec-extract-sig-3.c: Likewise.
* gcc.target/powerpc/bfp/vec-insert-exp-2.c: Likewise.
* gcc.target/powerpc/bfp/vec-insert-exp-3.c: Likewise.
* gcc.target/powerpc/bfp/vec-insert-exp-6.c: Likewise.
* gcc.target/powerpc/bfp/vec-insert-exp-7.c: Likewise.
* gcc.target/powerpc/bfp/vec-test-data-class-2.c: Likewise.
* gcc.target/powerpc/bfp/vec-test-data-class-3.c: Likewise.
* gcc.target/powerpc/byte-in-either-range-1.c: Likewise.
* gcc.target/powerpc/byte-in-range-1.c: Likewise.
* gcc.target/powerpc/byte-in-set-1.c: Likewise.
* gcc.target/powerpc/crypto-builtin-2.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-1.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-11.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-16.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-21.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-26.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-31.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-36.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-41.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-46.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-51.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-56.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-6.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-61.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-66.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-71.c: Likewise.
* gcc.target/powerpc/dfp/dtstsfi-76.c: Likewise.
* gcc.target/powerpc/vsu/vec-all-nez-7.c: Likewise.
* gcc.target/powerpc/vsu/vec-any-eqz-7.c: Likewise.
* gcc.target/powerpc/vsu/vec-cmpnez-7.c: Likewise.
* gcc.target/powerpc/vsu/vec-cntlz-lsbb-2.c: Likewise.
* gcc.target/powerpc/vsu/vec-cnttz-lsbb-2.c: Likewise.
* gcc.target/powerpc/vsu/vec-xl-len-12.c: Likewise.
* gcc.target/powerpc/vsu/vec-xlx-7.c: Likewise.
* gcc.target/powerpc/vsu/vec-xrx-7.c: Likewise.
* gcc.target/powerpc/vsu/vec-xst-len-12.c: Likewise.


Index: gcc/config/rs6000/rs6000-c.c
===
--- gcc/config/rs6000/rs6000-c.c(revision 250791)
+++ gcc/config/rs6000/rs6000-c.c(working copy)
@@ -6802,7 +6802,7 @@ altivec_resolve_overloaded_builtin (location_t loc
 if (unsupported_builtin)
   {
const char *name = rs6000_overloaded_builtin_name (fcode);
-   error ("Builtin function %s not supported in this compiler