Age | Commit message (Collapse) | Author |
|
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/
|
|
has vtable analysis
|
|
Fixes #852
|
|
|
|
Bump to 0.28
Brings in #822 which unblocks https://bugzilla.mozilla.org/show_bug.cgi?id=1366956,
and also #829 which should greatly reduce merge conflicts in checked in bindings.
|
|
|
|
Derive debug and opaque types
See each commit for details.
Follow up to #842.
r? @emilio or @Manishearth
|
|
|
|
|
|
And also not just fields, but also base members.
|
|
Useful for debugging when constraints go wrong.
|
|
There are lots of different ways that a type can end up being opaque, and it is
best to handle all the ways in one fell swoop, rather than check each different
ways (for example, if a struct has non-type template params, if a template
instantiation's template definition has them, etc...) for each different type
kind.
|
|
|
|
Never use spaces in generated name (fixes #844)
None
|
|
|
|
Remove whitelisted_items as arg to codegen funcs
Deals with #838
|
|
|
|
analysis: Account for template instantiations of opaque types in the derive debug analysis.
We have a special-case for them in codegen to generate a blob, that can derive
debug.
This is a regression from #824, and hit stylo.
|
|
debug analysis.
We have a special-case for them in codegen to generate a blob, that can derive
debug.
This is a regression from #824, and hit stylo.
|
|
ir: Track the codegen-reachable items, and use it instead of whitelisted_items() for code generation.
This standardizes the behavior change at #834, but without regressions.
I've added a few more tests for #833 here.
Closes #834.
|
|
whitelisted_items() for code generation.
This standardizes the behavior change at #834, but without regressions.
I've added a few more tests for #833 here.
|
|
ir: We really need to traverse all edges for the used template parameter analysis to be sound.
Fixes #833
|
|
Remove RUST_LOG=bindgen from the issue template
Neither Emilio nor I find it helpful, so lets rm -rf
|