summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2022-06-06tests: Make some other tests auto-update with BINDGEN_OVERWRITE_EXPECTED=1Emilio Cobos Álvarez
2022-06-05Skip input headers in Linguist statisticsDarren Kulp
[skip ci]
2022-06-05Skip generated files in Linguist statisticsDarren Kulp
[skip ci]
2022-06-05ir: Centralize must_use checks and simplify codegen.Emilio Cobos Álvarez
2022-06-05Look for `must_use` on typdefs in function returnIan Chamberlain
Closes #2206
2022-05-17Fix "dereferencing a null pointer" in C layout testsGavin Li
Instead of dereferencing a null pointer, create a MaybeUninit from which we can extract well-defined addresses.
2022-05-08Derive from any other trait only when deriving from CopyMichal Rostecki
It's impossible to #[derive] from any other trait when not deriving from Copy when using the newest Rust nightly. Any attempt to do that results in the following error: error: `#[derive]` can't be used on a `#[repr(packed)]` struct that does not derive Copy (error E0133) Fixes: #2083 Signed-off-by: Michal Rostecki <vadorovsky@gmail.com>
2022-04-19Use common type alias for anonymous enums in consts modeAlan Wu
Previously, anonymous enums generated a type alias but did not use it. For example the following: ```C enum { ZERO, ONE = 4999, }; ``` Generated this: ```Rust /* automatically generated by rust-bindgen 0.59.2 */ pub const ZERO: ::std::os::raw::c_uint = 0; pub const ONE: ::std::os::raw::c_uint = 4999; pub type _bindgen_ty_1 = ::std::os::raw::c_uint; ``` For use cases where humans look at bindgen's Rust output this was a little strange since it's a deviation from how the Rust output for named enums is organized, where all constants share the same type using the type alias. The unused type alias also triggered the dead_code lint. Change to use the generated type alias.
2022-03-15add attributes to dynamic functionsEmil Gardström
this includes comments and must_use annotations
2022-03-15disable test_clang_env_args on windowsEmil Gardström
2022-03-15disable some tests on windowsEmil Gardström
This is due to differences in representation of `signed long` and `unsigned long` on most Linux-based systems and Windows (`64` vs. `32` bits)
2022-03-15disable layout tests for `derive-custom` and `convert-cpp-comment-to-rust` testEmil Gardström
2022-03-15escape `\` in paths for tests modulesEmil Gardström
2022-03-15tests: Remove testing_only_libclang_4 and expectationsDarren Kulp
2022-03-15tests: Enable a test with a const template paramDarren Kulp
This should have been added in #2155 but was missed then.
2022-03-15Added support for `vectorcall` ABIDavid Cole
2022-03-15Fix macOS test expectationsSebastian Imlay
* Updated tests/expectations/Cargo.toml to use 2018 rust. * Added Debug and Copy to objective-c structs. * Fixed lifetimes in objective-c trait templates. * Fixed imports for objective-c expectations tests.
2022-02-18codegen: Use raw pointers rather than references in vtable functions.Emilio Cobos Álvarez
Closes #2163
2022-02-18Put vtable generation behind a flag for now.Emilio Cobos Álvarez
2022-02-18Add --allowlist-file optionDavid Drysdale
2022-02-18tests: Remove clang-3.9 expectationsDarren Kulp
2022-01-29Mark all vtable functions as `unsafe extern "C"`Justin Moore
2022-01-29On second thought, don't generate virtual destructorsDr. Chat
2022-01-29Mark all vtable functions as `pub`Dr. Chat
2022-01-29Account for virtual destructorsDr. Chat
2022-01-29Extremely basic Vtable generationDr. Chat
2021-12-29Remove deprecation and ReplaceMikuroXina
2021-12-29Replace generate with gen in testMikuroXina
2021-12-29codegen: Don't automatically derive Debug and Copy for non-rust enums.Emilio Cobos Álvarez
Fixes #2143
2021-12-07Fix warnings on testsMikuroXina
2021-11-26Add --blocklist-file option (#2097)David Drysdale
Update Item to hold a `clang::SourceLocation` and use this to allow blocklisting based on filename. The existing code has a special case that always maps <stdint.h> integer types to corresponding Rust integer types, even if the C types are blocklisted. To match this special case behaviour, also treat these C <stdint.h> types as being eligible for derived Copy/Clone/Debug traits. Fixes #2096
2021-11-26Drop 'static for pub const strings for rustc>1.17Alberto Planas
Constant and static declaration have a 'static live time by default, that is already elided since 1.17. Clippy complains on this kind of strings that are present in the generated code. This patch remove the 'static live time for those strings when rustc > 1.17 via a new added RustFeature. Fix #1612 Signed-off-by: Alberto Planas <aplanas@suse.com>
2021-10-30context: Escape the try keyword properlyFionera
2021-10-27Avoid case of a self-referential type alias.Adrian Taylor
This previously produced a type alias which referred to itself, which was clearly wrong and resulted in downstream code recursing infinitely. The problem case (per bug #2102) is: template <typename> class B{}; template <typename c> class C { public: using U = B<c>; }; class A : C<A> { U u; }; As far as I can tell, we parse clang's definition of B<A>; that leads us to parse A; to find it has a field U which turns out to be of type B<A>. And so we hit the line in item.rs which says: debug!("Avoiding recursion parsing type: {:?}", ty); and bail out, returning the original item ID: hence, a self- referential typedef is created. The 'fix' in this PR creates an opaque type in this case instead, to avoid later infinite loops. It would be preferable to avoid this situation in the first place, but presumably that would require us to split the parsing phase into two: 1) types 2) fields within those types. Fixes #2102.
2021-10-27Don't generate 2^64 byte padding fields on unionsTheodore Dubois
The --explicit-padding flag would make bindgen try to add tail padding to rust unions, by adding up the size of all the union fields and subtracting from the size of the union as given by clang. The total size of a union's fields is always larger than the union, so the subtraction underflowed and bindgen produced padding fields larger than addressable RAM.
2021-10-27Fix warningsMikuroXina
2021-08-24Detect and avoid cycles when resolving items.Patrick Walton
These can happen in certain cases involving incomplete qualified dependent types. To avoid looping forever, we need to check for them. Closes #2085.
2021-08-24Add testsChristian Vetter
2021-08-24Use annotations on enumerations: This enables users to add additional ↵Christian Vetter
derives, or prevent deriving traits Fixes #2076
2021-07-31Also implement div-style must_use_type annotation.Karel Peeters
2021-07-31Implement must_use_type commandline flag and builder option.Karel Peeters
2021-07-31Don't assume that an inner class declaration always immediately yields aPatrick Walton
complete type. It might not if we had to avoid recursion when processing types. Detect that case and bail out. This bug was being masked by the fact that we didn't always find definitions for the recursion check and so it didn't trigger, but now that this check is more reliable we have to be careful in more places. The test case was reduced from the GCC STL allocator definition.
2021-07-31Canonicalize types before looking for their definitions.Patrick Walton
In some esoteric cases involving nested templates, `ty.declaration().definition()` isn't enough to find the definition: we need `ty.canonical_type().declaration().definition()` instead. Closes #2078.
2021-07-26docs: Fix rustfmt install steps.Emilio Cobos Álvarez
Fixes #2080
2021-07-26codegen: Don't check large_arrays to generate bitfield ctors because they ↵Emilio Cobos Álvarez
use the Default trait. Fixes #2082
2021-07-16Let Rust derive everything but Default for large arrays in 1.47 and laterIan P. Cooke
Fixes #1977 as of rust-lang/rust#74060 is available since Rust 1.47 Fixes #2041. Closes #2070.
2021-07-16Allow explicit padding (#2060)Eric Seppanen
If a struct needs to be serialized in its native format (padding bytes and all), for example writing it to a file or sending it on the network, then explicit padding fields are necessary, as anything reading the padding bytes of a struct may lead to Undefined Behavior.
2021-06-21comp: Do a better effort of computing packedness before bitfield units.Emilio Cobos Álvarez
Fixes #2067
2021-05-18Identify forward declarations in params. (#2052)Adrian Taylor
2021-05-11Zero out padding in custom Default trait implementations (#2051)Daniel Xu
* Zero out padding in custom Default trait implementations Previously, we were using `std::mem::zeroed()` which unfortunately does not necessarily zero out padding. It'd be better if the padding is zeroed out because some libraries are sensitive to non-zero'd out bytes, especially when forward/backward compatability is involved. This commit ensures all bytes are zeroed out in custom Default trait implementations.