about summary refs log tree commit diff
path: root/src/rustllvm/ExecutionEngineWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-05-27 10:21:11 +0000
committerbors <bors@rust-lang.org>2015-05-27 10:21:11 +0000
commitf56782ab9c8d0f64b9a714cc24d925a81ac3211b (patch)
tree4a37d4c5cb459873a50f61325b9f135c40c9932d /src/rustllvm/ExecutionEngineWrapper.cpp
parenteb16ad6e71172eabb71acb73758675f25df91649 (diff)
parent677367599e8383c355b8e8261cafe3ce44c9c6de (diff)
downloadrust-f56782ab9c8d0f64b9a714cc24d925a81ac3211b.tar.gz
rust-f56782ab9c8d0f64b9a714cc24d925a81ac3211b.zip
Auto merge of #25762 - dotdash:codegen_test, r=alexcrichton
The current codegen tests only compare IR line counts between similar
rust and C programs, the latter getting compiled with clang. That looked
like a good idea back then, but actually things like lifetime intrinsics
mean that less IR isn't always better, so the metric isn't really
helpful.

Instead, we can start doing tests that check specific aspects of the
generated IR, like attributes or metadata. To do that, we can use LLVM's
FileCheck tool which has a number of useful features for such tests.

To start off, I created some tests for a few things that were recently
added and/or broken.
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions