llvm-project

Commit Graph

Author	SHA1	Message	Date
Petr Hosek	eb46c95c3e	[CMake] Use normalized Windows target triples Changes the default Windows target triple returned by GetHostTriple.cmake from the old environment names (which we wanted to move away from) to newer, normalized ones. This also requires updating all tests to use the new systems names in constraints. Differential Revision: https://reviews.llvm.org/D47381 llvm-svn: 339307	2018-08-09 02:16:18 +00:00
Filipe Cabecinhas	3ccd23e116	Use %run for running CFI tests Reviewers: pcc, krasin, eugenis Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D38412 llvm-svn: 314659	2017-10-02 10:21:26 +00:00
Ivan Krasin	a425623dd9	CFI: add XFAIL test for a future optimization of two vcalls. Summary: Often, a code will call multiple virtual methods of a given object. If they go in a linear block, it should be possible to check vtable before the first call, then store vtable pointer and reuse it for the second vcall without any additional checks. This is expected to have a positive performance impact on a hot path in Blink, see https://crbug.com/634139. Reviewers: kcc Differential Revision: https://reviews.llvm.org/D23151 llvm-svn: 277795	2016-08-05 01:45:54 +00:00

Author

SHA1

Message

Date

Petr Hosek

eb46c95c3e

[CMake] Use normalized Windows target triples

Changes the default Windows target triple returned by
GetHostTriple.cmake from the old environment names (which we wanted to
move away from) to newer, normalized ones. This also requires updating
all tests to use the new systems names in constraints.

Differential Revision: https://reviews.llvm.org/D47381

llvm-svn: 339307

2018-08-09 02:16:18 +00:00

Filipe Cabecinhas

3ccd23e116

Use %run for running CFI tests

Reviewers: pcc, krasin, eugenis

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D38412

llvm-svn: 314659

2017-10-02 10:21:26 +00:00

Ivan Krasin

a425623dd9

CFI: add XFAIL test for a future optimization of two vcalls.

Summary:
Often, a code will call multiple virtual methods of a given object.
If they go in a linear block, it should be possible to check vtable
before the first call, then store vtable pointer and reuse it for
the second vcall without any additional checks.

This is expected to have a positive performance impact on a hot
path in Blink, see https://crbug.com/634139.

Reviewers: kcc

Differential Revision: https://reviews.llvm.org/D23151

llvm-svn: 277795

2016-08-05 01:45:54 +00:00

3 Commits