afd7b69658
Revert "Disable swiftcall test on windows: More brutal way to appease windows bots"
...
This reverts commit r284174. The tests pass for me locally. It must have
been a 2015 only crash.
Fixes PR30699
llvm-svn: 284781
2016-10-20 21:17:28 +00:00
b715eb4504
Add more swift calling convention tests
...
llvm-svn: 284285
2016-10-14 21:55:56 +00:00
18fad46fe3
Disable swiftcall test on windows: More brutal way to appease windows bots
...
The backtrace on the bot does not give me any indication what is wrong.
The test case interestingly passes in stage2 of the build.
I don't have a way of debugging this.
Disable the test on windows and hope if there is truly a bug in the code that
was causing we will eventually run into this on other platforms.
llvm-svn: 284174
2016-10-13 22:47:03 +00:00
c45025e763
Add required targets to tests to (hopefully) appease bots
...
llvm-svn: 284162
2016-10-13 20:59:23 +00:00
3d01ad116c
Swift Calling Convention: Fix out of bounds access
...
Use iterator instead of address of element in vector
It is not valid to access one after the last element.
rdar://28759508
llvm-svn: 284150
2016-10-13 19:19:37 +00:00
2d556f2d06
Add more 64bit swiftcall convention tests
...
llvm-svn: 284133
2016-10-13 17:17:36 +00:00
Reid Kleckner