summaryrefslogtreecommitdiffstats
path: root/clang/test/CodeGen/altivec.c
Commit message (Collapse)AuthorAgeFilesLines
* Remove the -faltivec alias option and replace it with -maltivec everywhere.Eric Christopher2017-03-211-1/+1
| | | | | | | | | | | The alias was only ever used on darwin and had some issues there, and isn't used in practice much. Also fixes a problem with -mno-altivec not turning off -maltivec. Also add a diagnostic for faltivec/fno-altivec that directs users to use maltivec options and include the altivec.h file explicitly. llvm-svn: 298449
* Remove some incorrect test suppressionsAlp Toker2014-06-301-1/+0
| | | | | | | | | These don't actually require any registered backend to run. This commit tests the water with a handful of fixes for what is a more widespread problem. llvm-svn: 212008
* clang/test: REQUIRES: s/ppc{32|64}-registered-target/powerpc-registered-target/NAKAMURA Takumi2013-12-041-1/+1
| | | | llvm-svn: 196349
* Tests: check for target availability for target-specific tests.Jim Grosbach2012-07-091-0/+1
| | | | | | | | Lots of tests are using an explicit target triple w/o first checking that the target is actually available. Add a REQUIRES clause to a bunch of them. This should hopefully unbreak bots which don't configure w/ all targets enabled. llvm-svn: 159949
* Add support for bitcasts to vector type in Evaluate.Eli Friedman2011-12-221-4/+4
| | | | llvm-svn: 147137
* Move vector bitcast handling in constant expressions from the expressionRichard Smith2011-12-061-0/+9
| | | | | | | | | | | | | evaluator into constant initializer handling / IRGen. The practical consequence of this is that the bitcast now lives in the constant's definition, rather than in its uses. The code in the constant expression evaluator was producing vectors of the wrong type and size (and possibly of the wrong value for a big-endian int-to-vector bitcast). We were getting away with this only because we don't yet support constant-folding of any expressions which inspect vector values. llvm-svn: 145981
* Don't emit nsw flags for vector operations; there's basically no benefit, ↵Eli Friedman2011-05-061-1/+1
| | | | | | and a lot of downside (like PR9850, which is about clang's xmmintrin.h making an unexpected transformation on an expression involving _mm_add_epi32). llvm-svn: 131000
* supported: AltiVec vector initialization with a single literal according to ↵Anton Yartsev2011-03-271-2/+29
| | | | | | PIM section 2.5.1 - after initialization all elements have the value specified by the literal llvm-svn: 128375
* Fix the constant evaluator for AltiVec-style vector literals so that theJohn McCall2010-06-111-0/+4
vector is filled with the given constant; we were just initializing the first element. llvm-svn: 105824
OpenPOWER on IntegriCloud