https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
Alexander Monakov changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #11 from Alexander Monakov ---
Author: amonakov
Date: Mon Feb 4 15:00:41 2019
New Revision: 268522
URL: https://gcc.gnu.org/viewcvs?rev=268522&root=gcc&view=rev
Log:
doc: showcase a "union of vectors" pattern (PR 88698)
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #10 from Devin Hussey ---
Well what about a special type attribute or some kind of transparent_union like
thing for Intel's types? It seems that Intel's intrinsics are the main (only)
platform that uses generic types.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #9 from Marc Glisse ---
(In reply to Devin Hussey from comment #2)
> What I am saying is that I think -flax-vector-conversions should be default,
> or we should only have minimal warnings instead of errors.
>
> That will make generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #8 from Andrew Pinski ---
(In reply to Devin Hussey from comment #7)
> I mean, sure, but how about this?
>
> What about meeting in the middle?
The problem is how do you implement the rules that are required by both the
Altivec and N
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #7 from Devin Hussey ---
I mean, sure, but how about this?
What about meeting in the middle?
-fno-lax-vector-conversions generates errors like it does now.
-flax-vector-conversions shuts GCC up.
No flag causes warnings on -Wpedanti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #5 from Devin Hussey ---
Well, if we are aiming for strict compliance, might as well throw out every GCC
extension in existence (including vector extensions), those aren't strictly
compliant to the C/C++ standard. /s
The whole point
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #4 from Andrew Pinski ---
(In reply to Devin Hussey from comment #2)
> It is to be noted that Clang has -Wvector-conversion, which is the
> equivalent of -fno-lax-vector-conversions, however, it is a warning that
> only occurs with -W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #3 from Andrew Pinski ---
At one point -flax-vector-conversions was default and did the option did not
exist.
https://gcc.gnu.org/ml/gcc/2006-10/msg00682.html
See also:
https://gcc.gnu.org/ml/gcc/2006-11/msg00051.html
NOTE havin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #2 from Devin Hussey ---
What I am saying is that I think -flax-vector-conversions should be default, or
we should only have minimal warnings instead of errors.
That will make generic vectors much easier to use.
It is to be noted th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #1 from Marc Glisse ---
It would help if you could write some (very short) functions illustrating the
behavior you are requesting. "convert", "compatible" all depend about the
context in which they appear.
12 matches
Mail list logo
