-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix nm #84
Fix nm #84
Conversation
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.
@homunkulus r+ |
📌 Commit 3b8dedd has been approved by |
@japaric is there a log of these failures somewhere? Does it look like the same sort of issue we were having with the gnueabihf targets? |
@mattico arm-unknown-linux-gnueabi
I don't know if the other arm targets were also failing.
I'm not sure but the same intrinsics are failing, right? addsf3 and adddf3. |
Ah, but both the vs compiler_rt and vs gcc_s tests are failing so it's different. On gnueabihf only vs gcc_s was failing iirc. |
Ah, mips-gnu and mipsel-gnu were also failing 🙀. |
So there's probably a real issue somewhere. Not looking forward to debugging that... |
💔 Test failed - status-travis |
It might be a good idea to remove the add impl for now since it's still broken but the old tests didn't catch it. It might randomly fail if the U{32,64} quickcheck randomly generates a small denormal. |
@homunkulus try |
@homunkulus r+ |
📌 Commit d0a57cb has been approved by |
@homunkulus r+ |
📌 Commit 89ebc46 has been approved by |
☀️ Test successful - status-appveyor, status-travis |
84: Implement fmod r=japaric a=P1n3appl3 closes rust-lang#21 I replaced the `isnanf()` function from `fmodf()` with a call to the core function `is_nan()`. If there's a reason we needed to re-implement it then I can change that back. Also I couldn't figure out what to do in `src/lib.rs`. Is the `#[cfg(todo]` that I should be removing the one for `mod_euc()`? If so why is the equivalent one for the `f64` version still there? Co-authored-by: Joseph Ryan <[email protected]> Co-authored-by: Jorge Aparicio <[email protected]>
We were actually running
ci/run.sh
withoutset -e
and we were ignoring test failures and failed commands 🙀.This also undoes #48 which introduced test failures in addsf3 and adddf3 for the arm-unknown-linux-gnueabi target. Sorry @mattico!