llvm-project

Commit Graph

Author	SHA1	Message	Date
Ehsan Amiri	a538b0f023	Adding -verify-machineinstrs option to PowerPC tests Currently we have a number of tests that fail with -verify-machineinstrs. To detect this cases earlier we add the option to the testcases with the exception of tests that will currently fail with this option. PR 27456 keeps track of this failures. No code review, as discussed with Hal Finkel. llvm-svn: 277624	2016-08-03 18:17:35 +00:00
James Y Knight	38514d2177	Fix test added in r236850 for OSX builders. Need to specify triple so that llvm emits the asm syntax that the test expected. llvm-svn: 236855	2015-05-08 14:04:54 +00:00
James Y Knight	284e7b3d6c	Fix alignment checks in MergeConsecutiveStores. 1) check whether the alignment of the memory is sufficient for the merged store or load to be efficient. Not doing so can result in some ridiculously poor code generation, if merging creates a vector operation which must be aligned but isn't. 2) DON'T check that the alignment of each load/store is equal. If you're merging 2 4-byte stores, the first might have 8-byte alignment, but the second certainly will have 4-byte alignment. We do want to allow those to be merged. llvm-svn: 236850	2015-05-08 13:47:01 +00:00

Author

SHA1

Message

Date

Ehsan Amiri

a538b0f023

Adding -verify-machineinstrs option to PowerPC tests

Currently we have a number of tests that fail with -verify-machineinstrs.
To detect this cases earlier we add the option to the testcases with the
exception of tests that will currently fail with this option. PR 27456 keeps
track of this failures.

No code review, as discussed with Hal Finkel.

llvm-svn: 277624

2016-08-03 18:17:35 +00:00

James Y Knight

38514d2177

Fix test added in r236850 for OSX builders.

Need to specify triple so that llvm emits the asm syntax that the
test expected.

llvm-svn: 236855

2015-05-08 14:04:54 +00:00

James Y Knight

284e7b3d6c

Fix alignment checks in MergeConsecutiveStores.

1) check whether the alignment of the memory is sufficient for the
*merged* store or load to be efficient.

Not doing so can result in some ridiculously poor code generation, if
merging creates a vector operation which must be aligned but isn't.

2) DON'T check that the alignment of each load/store is equal. If
you're merging 2 4-byte stores, the first *might* have 8-byte
alignment, but the second certainly will have 4-byte alignment. We do
want to allow those to be merged.

llvm-svn: 236850

2015-05-08 13:47:01 +00:00

3 Commits