diff options
| author | bors <bors@rust-lang.org> | 2015-08-22 21:33:35 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-08-22 21:33:35 +0000 |
| commit | 357ae03cc318584402a090d4bbf74ea23ed69106 (patch) | |
| tree | 9caa4da28a7a1a842c18d8e0af52627cf6e4bfd4 /src/rustllvm/RustWrapper.cpp | |
| parent | 8278342a8799db8c650b44ad0275e6be2c92df52 (diff) | |
| parent | 2ac5cc4863171c1eb456d4f750690e0b955221f1 (diff) | |
| download | rust-357ae03cc318584402a090d4bbf74ea23ed69106.tar.gz rust-357ae03cc318584402a090d4bbf74ea23ed69106.zip | |
Auto merge of #27914 - pnkfelix:fix-fcnr-for-valgrind, r=alexcrichton
Fix (and extend) src/test/run-pass/foreign-call-no-runtime.rs While going over various problems signaled by valgrind when running `make check` on a build configured with `--enable-valgrind`, I discovered a bug in this test case. Namely, the test case was previously creating an `i32` (originally an `int` aka `isize` but then we changed the name and the fallback rules), and then reading from a `*const isize`. Valgrind rightly complains about this, since we are reading an 8 byte value on 64-bit systems, but in principle only 4 bytes have been initialized. (I wish this was the only valgrind unclean test, but unfortunately there are a bunch more. This was just the easiest/first one that I dissected.)
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
