09d61e8f97
More small updates to the README
2016-10-14 15:50:50 -07:00
9b6f5ff4cd
Update CI configs
...
* Run on the master branch (to get previews)
* Pass --target on AppVeyor (oops)
* Use the current nightly for arm (I think that bug is fixed)
2016-10-14 11:58:40 -07:00
8c3e0ae3e8
Auto merge of #102 - alexcrichton:update, r=alexcrichton
...
Update webhook url
2016-10-14 11:52:29 -07:00
ae178cee6e
Update webhook url
2016-10-14 11:44:45 -07:00
ef08913bc8
Merge pull request #99 from japaric/ppc64le
...
fix the powerpc64le target
2016-10-14 13:11:18 -05:00
5d164a4eda
fix the powerpc64le target
...
by selecting a CPU that's compatible with the instructions that `rustc`
generates
2016-10-14 09:59:21 -05:00
f6b5c56113
README: remove the Contribution sub-section
...
which still referred to the Apache-2 license and is now deprecated by
the updated License section
cc @brson
2016-10-13 20:51:50 -05:00
1221ff3b04
Merge pull request #98 from brson/lic
...
Correct the license to that of upstream compiler-rt
2016-10-13 12:22:06 -05:00
c064549c4b
Correct the license to that of upstream compiler-rt
...
As this is a derivative work we must maintain the same license terms.
2016-10-12 17:50:39 +00:00
e441058be7
ci/run.sh: remove debug stuff
2016-10-10 20:53:21 -05:00
a163ca7ac3
fix more warnings
2016-10-10 20:21:11 -05:00
e05caa1227
fix warnings
2016-10-10 19:45:34 -05:00
8f0847eb94
rename to compiler_builtins, add rust-lang/rust-ish crate attributes
2016-10-10 19:05:21 -05:00
24c0247c6a
add the compiler_builtins feature to src/lib.rs
2016-10-10 16:45:24 -05:00
d2a3c45a29
set crate_name and crate_type in src/lib.rs
2016-10-10 16:43:38 -05:00
4bf128a84c
add a rustbuild cargo feature for integration with rust-lang/rust
2016-10-10 16:18:18 -05:00
c56faf22ab
Merge pull request #80 from japaric/abort
...
panic! -> abort
2016-10-07 18:55:51 -05:00
96ddd4ed8d
use test::black_box instead of ptr::*_volatile
...
both prevent LLVM from optimizing away the intrinsics but the former
doesn't produce an `intrinsics` binary that segfaults
2016-10-07 18:26:21 -05:00
c82403551d
fix unsafe warnings
2016-10-07 18:19:40 -05:00
fd69beba29
get profile.dev (-debug-assertions) + LTO working
2016-10-07 18:19:40 -05:00
a21fb956f9
insert more `abort()` calls where division by zero may occur
2016-10-07 18:19:40 -05:00
a2ffc799d0
check that we don't have any call to panic in our implementations
2016-10-07 18:19:40 -05:00
534d22e287
panic! -> abort
...
closes #79
2016-10-07 18:19:40 -05:00
24c2a15f3d
fix path to .rlib on OSX
2016-10-07 15:03:22 -05:00
3e6ebb3b76
run the full test suite on osx
2016-10-07 12:03:59 -05:00
1c9094814d
pass -nostartfiles to the linker
2016-10-07 07:13:55 -05:00
213d929f86
drop the target files
2016-10-06 23:20:09 -05:00
6726a8c569
Merge pull request #93 from japaric/nightly-up
...
switch to a current nightly
2016-10-05 23:01:24 -05:00
5908bb7f87
switch back to old nightly for the arm-gnueabi target
2016-10-05 22:13:55 -05:00
4df5deba44
switch to a current nightly
2016-10-05 21:34:16 -05:00
2706d9264a
switch compiler-rt to rust-lang's fork
...
this fork has been patched against the UB in floatsidf and floasisf
closes #85
2016-10-03 23:26:49 -05:00
8652c66bdc
Auto merge of #82 - mattico:add_pow, r=japaric
...
Add pow functions
I still want to clean up the commit history, but otherwise I think this is complete. ~~Can you run the tests on it?~~
2016-10-04 01:52:27 +00:00
ff7e3ba2c0
stop compiling compiler-rt implementations
...
to avoid duplicate symbols
2016-10-03 20:52:14 -05:00
8a32bd3424
fix duplicate symbol test
2016-10-03 20:20:23 -05:00
77bca82434
bump rustc-cfg version and show a better error message when it fails
2016-10-03 19:25:32 -05:00
6622c49be6
Implement powi_f2
2016-10-03 11:20:42 -05:00
954e3b7095
Auto merge of #86 - mattico:multitester, r=japaric
...
Initial implementation of multitester
Implements part of #72 .
I wanted to work on this first because it should help me find the problem in the add implementation.
Test failures now look like this:
```
__addsf3 - Args: 1 1264853201
rustc-builtins: Some(0)
compiler_rt: Some(14950609)
gcc_s: None
__addsf3 - Args: 1 632426600
rustc-builtins: Some(0)
compiler_rt: Some(0.00000000000000030889195)
gcc_s: None
__addsf3 - Args: 1 316213300
rustc-builtins: Some(0)
compiler_rt: Some(0.0000000000000000000000000013696648)
gcc_s: None
[snip]
thread 'float::add::tests::_test::__addsf3' panicked at '[quickcheck] TEST FAILED. Arguments: (1, 1)', /home/matt/.cargo/registry/src/github.com-1ecc6299db9ec823/quickcheck-0.3.1/src/tester.rs:118
```
It currently prints all of the errors, if that's undesirable we'd need to remove the shrinkers or modify quickcheck.
2016-10-03 06:58:30 +00:00
0827f8c7f1
hide the thumbv* target files
...
due to how Cargo works, the rustc-cfg in build.rs was picking our target
specifications rather than the one the user meant to use. Placing our
target files in any place other than the root of the Cargo project
avoids the issue.
2016-10-02 19:23:54 -05:00
02140cddc9
Initial implementation of multitester
2016-10-02 14:38:40 -05:00
89ebc46f37
pick target during Xargo installation
2016-09-30 20:41:59 -05:00
d0a57cb871
give Xargo a $HOME
2016-09-30 20:21:15 -05:00
fb5cb0e4c1
fix Xargo installation
2016-09-30 20:20:15 -05:00
d8fa45a653
add back the mysterious apt-get install qemu-user-static
2016-09-30 20:08:29 -05:00
3b8dedd416
Revert "Merge pull request #48 from mattico/add_float_quickcheck"
...
This reverts commit e34a6058dfcab88e6133
2016-09-30 19:12:17 -05:00
36a437a445
fix nm call
...
the prefix was missing a '-', i.e. arm-linux-gnueabinm was being called.
This also sets -e in run.sh to catch this sort of errors.
2016-09-30 19:04:48 -05:00
960f7a80ad
Merge pull request #81 from japaric/cache
...
cache Cargo artifacts
2016-09-30 19:00:06 -05:00
b60d2515ff
use `docker run --user` instead of manually creating a user
2016-09-30 18:37:41 -05:00
d2036122f1
/home/travis -> $HOME
2016-09-30 18:25:40 -05:00
0c9b651389
do chmod jut before the script phase ends
2016-09-30 18:09:52 -05:00
43e019dfc4
cache Cargo artifacts
...
notable changes in the docker-based testing infrastructure
- the docker containers can now modify $CARGO_HOME, to re-use the outer
Cargo registry, and the target directory to re-use build artifacts.
- the docker containers are removed when their execution finishes
because it's no longer necessary to re-start them to inspect them
because all the interesting output is in the outer target directory
2016-09-30 17:39:36 -05:00
Alex Crichton
bors
Jorge Aparicio
Brian Anderson
homunkulus
Matt Ickstadt
Matt Ickstadt