summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2022-10-04split the repo into a workspaceChristian Poveda
remove `clap` dependency :tada: update the book installation instructions
2022-10-03address clippy lintsChristian Poveda
2022-10-03Merge pull request #2285 from ferrous-systems/clone-optionsChristian Poveda
Make `BindgenOptions` clonable
2022-10-03remove referenceChristian Poveda
2022-10-02Enables blocklisting of Objective-C methodsCameron Mulhern
2022-09-28Don't traverse through special-cased <stdint.h> types.Geoffry Song
2022-09-27split `processing` moduleChristian Poveda
2022-09-26make `BindgenOptions` clonableChristian Poveda
2022-09-26s/static/constChristian Poveda
2022-09-23Clean-up postprocessing to use less macro magic.Emilio Cobos Álvarez
2022-09-23move codegen postprocessing to its own moduleChristian Poveda
2022-09-23Map size_t to usize by default and check compatibility (fixes #1901, #1903)Geoffrey Thomas
This addresses the underlying issue identified in #1671, that size_t (integer that can hold any object size) isn't guaranteed to match usize, which is defined more like uintptr_t (integer that can hold any pointer). However, on almost all platforms, this is true, and in fact Rust already uses usize extensively in contexts where size_t would be more appropriate, such as slice indexing. So, it's better for ergonomics when interfacing with C code to map the C size_t type to usize. (See also discussion in rust-lang/rust#65473 about how usize really should be defined as size_t, not uintptr_t.) The previous fix for #1671 removed the special case for size_t and defaulted to binding it as a normal typedef. This change effectively reverts that and goes back to mapping size_t to usize (and ssize_t to isize), but also ensures that if size_t is emitted, the typedef'd type of size_t in fact is compatible with usize (defined by checking that the size and alignment match the target pointer width). For (hypothetical) platforms where this is not true, or for compatibility with the default behavior of bindgen between 0.53 and this commit, onwards, you can disable this mapping with --no-size_t-is-usize.
2022-09-22features: Bump LATEST_STABLE_RUST after #2267.Emilio Cobos Álvarez
2022-09-22update to rust 1.64Christian Poveda
2022-09-22use `#[feature(core_ffi_c)]` when availableChristian Poveda
2022-09-22codegen: Implement manuallydrop fields better.Emilio Cobos Álvarez
This doesn't change behavior but makes the code make more sense.
2022-09-23Add option to deduplicate extern blocks (#2258)Christian Poveda
2022-09-23Option to wrap union members in ManuallyDrop (#2185)Poliorcetics
2022-09-22handle `__attribute__((noreturn))` attributeChristian Poveda
2022-09-22handle c++ `[[noreturn]]` attributeChristian Poveda
2022-09-22bring back optional cursor kindChristian Poveda
2022-09-22document `has_attrs`Christian Poveda
2022-09-22document `Attribute`Christian Poveda
2022-09-22find all attributes in a single passChristian Poveda
2022-09-22gate `_Noreturn` detection behind `--enable-fucntion-attribute-detection`Christian Poveda
2022-09-22add `CxTokenKind` argument to `has_attr`Christian Poveda
2022-09-22check for noreturn attributeChristian Poveda
2022-09-22add `is_divergent` fieldChristian Poveda
2022-09-18fix `--newtype-global-enum` optionChristian Poveda
2022-09-11add `--newtype-global-enum` optionChristian Poveda
2022-09-09add `BindgenOptions::require_syn` methodChristian Poveda
2022-09-08fix clippy lintsChristian Poveda
2022-09-05replace the `TraversalPredicate` trait with an alias typeChristian Poveda
2022-09-01address clippy lintsChristian Poveda
2022-08-25Generate opaque type for template param dependent bit field widthCollin Baker
libclang's API does not provide a straightforward way to check for this, and calling clang_getFieldDeclBitWidth is actively unsafe in this case. See https://github.com/llvm/llvm-project/issues/56644 We probably can't generate reasonable bindings for such a type, so make the binding opaque. Ideally libclang would report if the bit width could not be evaluated. Unfortunately making such a change would mean bumping the minimum libclang version from 6.0 to 15.0. Instead, add logic to traverse the AST subtree starting from the field's bit width specifier looking for template parameters. If we find one, we make the resulting type opaque.
2022-08-25Sorting the output semantically (#2254)Amanjeev Sethi
Generated code needs some sorting in a way that is semantically appealing. The request[1] asks for basic sorting like "types are declared first, then all structs, then all consts, then all function signatures, etc. [1] https://github.com/rust-lang/rust-bindgen/issues/1743 Signed-off-by: Amanjeev Sethi <aj@amanjeev.com> Co-authored-by: Christian Poveda <christian.poveda@ferrous-systems.com> Co-authored-by: Darren Kulp <darren@kulp.ch>
2022-08-18rustfmtChristian Poveda
2022-08-18emit warnings laterChristian Poveda
2022-08-18remove macro in favor of a methodChristian Poveda
2022-08-18store warnings and emit them laterChristian Poveda
2022-07-27adds 'await' to list of matches in 'rust_mangle'Bryn M. Reeves
2022-07-25ty: Use canonical type to access pointee.Emilio Cobos Álvarez
Using the canonical type fixes this but changes the output of some tests (in particular, pointer to typedefs now point to the underlying type). So do this only in known-bad cases. Fixes #2244
2022-07-16Don't use `Arg::takes_value` when it's implied by other calls.Jim Blandy
Both `Arg::value_name` and `Arg::number_of_values` imply `Arg::takes_value`, so those calls are just noise.
2022-07-16Add revision suggestion for MSRV >= 1.59.0onalante-msft
2022-07-16Extract pointer once for all alignment testsonalante-msft
2022-07-16Only insert uninit_decl if check_field_offset is non-emptyonalante-msft
2022-07-16rustfmtonalante-msft
2022-07-16Remove functions, use same uninit for all field testsonalante-msft
2022-07-16Place field alignment test functions before statementsonalante-msft
Clears clippy::items_after_statements warning for tests.
2022-06-06codegen: tests: Put each individual field test in a function.Emilio Cobos Álvarez
So that rustc doesn't take too much stack space without optimizations. Fixes #2218