Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
ci: Cache LLVM builds.
Fixes #896
|
|
Fixes #896
|
|
fix test for explicitly typed enum on aarch64
Fixes #893
|
|
|
|
Fix test expectations
r? @photoszzt
cc @tmfink: I had to revert the target features commit because there were a bunch of compilation failures in the test expectations (we had another, earlier regression that accidentally made it so that we weren't compiling and running the test expectations in CI, so we didn't catch the target features PR's regressions).
|
|
Fixes a regression from d73507e which accidentally broke this.
|
|
This reverts commit 0bb7b9f1c4652f63f41eba4064b79c044fd3d955.
It turns out our CI stopped running test expectations in an earlier
regression (from d73507e; fix incoming) and so this pull request actually
introduced a bunch of failures when compiling the test expectations and running
their unit tests :(
|
|
Feature 832 custom rust target
Addresses #832.
Instead of specifying whether or not to use stable, specify the Rust
release to support (one of several stable/beta releases or nightly).
The `--unstable-rust` option is still accepted and implies `--rust-target nightly`.
The definitions of `RustTarget` and `RustFeatures` are created with
macros.
In order to keep the test outputs the same,
`bindgen-flags: --rust-target 1.0` was added to test headers.
**Todo:**
- [x] Create `RustFeatures`/`RustTarget` structs
- [x] Replace uses of `unstable` with `RustFeatures` query
- [x] Add new tests
- [x] Fix doc comments TODOs
|
|
Instead of specifying whether or not to use stable, specify the Rust
release to support (one of several stable/beta releases or nightly).
The --unstable-rust option is still accepted and implies nightly.
The definitions of `RustTarget` and `RustFeatures` are created with
macros.
For each test that uses unions, there is a version that uses the latest
stable release and stable 1.0.
|
|
Fix recursive whitelisting and handling of opaque for derive default
Fix regression of derive default analysis.
Also fix opaque handing exposed by the above fix. r? @fitzgen
|
|
Can derive copy analysis
r? @fitzgen or @emilio. Fix: #766
|
|
|
|
Clean up trivially derive debug
r? @fitzgen
|
|
|
|
Fix regression of derive default analysis.
Also fix opaque handing exposed by the above fix.
|
|
Support deriving copy for large array
Fixes #56
|
|
|
|
|
|
Clean up left over derive debug nits
r? @fitzgen
|
|
|
|
Can derive default analysis
r? @fitzgen
|
|
Add a template for release announcements
And a script to find all the folks who contributed to the release.
Anything we should add or remove to the release announcement template? Once we've hashed this out, I'll make the first release announcement thread on u.r-l.o :-)
r? @emilio @nrc
|
|
And a script to find all the folks who contributed to the release.
|
|
Stablize name of pointer and array
This fixes #871.
|
|
|
|
Remove the incomplete `--dummy-uses` feature
This would generate dummy uses of all the whitelisted types, which we were planning on eventually using to generate DWARF for more layout testing of our types, but we decided that isn't worth the trouble. Kill it!
r? @emilio
|
|
This would generate dummy uses of all the whitelisted types, which we were
planning on eventually using to generate DWARF for more layout testing of our
types, but we decided that isn't worth the trouble. Kill it!
|
|
lib: Filter out include paths when looking for clang paths.
Fixes #848
|
|
|
|
|
|
|
|
Remove unused `Extra` associated types
r? @photoszzt or @emilio
|
|
Similar to `HasVtable::Extra`, it is no longer needed.
|
|
|
|
This is a throwback from the old, ad-hoc computation before we used the fixpoint
analysis.
|
|
|
|
Report what the unknown generate item was when parsing `--generate`
r? @emilio
|
|
|
|
Be conservative about deriving Debug/Default with large alignment
|
|
When there is large enough alignment that we might generate padding which has
more members that `RUST_DERIVE_IN_ARRAY_LIMIT`, we can break our ability to
derive traits. This commit solves this issue conservatively: there are cases
where we leave a derive on the table, because in order to know that we could add
that derive, we would need to compute padding before we determine whether we can
derive.
Fixes #648
|
|
Setup Appveyor
|
|
|
|
Pull out the loop that generates dependency map into its own function.
|
|
|
|
Missed the most important part of the last commit... r=me
|
|
s/servo/rust-lang-nursery/ \o/
|