llvm-project.git/llvm/lib/Transforms/Instrumentation/DataFlowSanitizer.cpp, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [NFC] Use `llvm::includes` instead of `std::includes` (#143542) 2025-06-12T01:27:27+00:00 Longsheng Mou longshengmou@gmail.com 2025-06-12T01:27:27+00:00 52360d195b85608c677d781272534dfa61e9a1c3 This PR follows up #143297. 
This PR follows up #143297.
 IR: Make Module::getOrInsertGlobal() return a GlobalVariable. 2025-05-27T19:23:12+00:00 Peter Collingbourne peter@pcc.me.uk 2025-05-27T19:23:12+00:00 645f0e6723f21aef8099d8d65f5719fd9feb125e After pointer element types were removed this function can only return a GlobalVariable, so reflect that in the type and comments and clean up callers. Reviewers: nikic Reviewed By: nikic Pull Request: https://github.com/llvm/llvm-project/pull/141323 
After pointer element types were removed this function can only return
a GlobalVariable, so reflect that in the type and comments and clean
up callers.

Reviewers: nikic

Reviewed By: nikic

Pull Request: https://github.com/llvm/llvm-project/pull/141323
[Transforms] Use *Set::insert_range (NFC) (#132652) 2025-03-24T02:42:53+00:00 Kazu Hirata kazu@google.com 2025-03-24T02:42:53+00:00 73dc2afd2c334aac735caba94292052d63014c9d We can use *Set::insert_range to collapse: for (auto Elem : Range) Set.insert(E); down to: Set.insert_range(Range); In some cases, we can further fold that into the set declaration. 
We can use *Set::insert_range to collapse:

  for (auto Elem : Range)
    Set.insert(E);

down to:

  Set.insert_range(Range);

In some cases, we can further fold that into the set declaration.
 [DFSan] Change placeholders from `undef` to `poison` (#131534) 2025-03-17T22:16:47+00:00 Pedro Lobo pedro.lobo@tecnico.ulisboa.pt 2025-03-17T22:16:47+00:00 1b31646757777c8ef68932ac61084b4bd7af2bc1 Use `poison` to create dummy phi nodes instead of `undef`. 
Use `poison` to create dummy phi nodes instead of `undef`.
 [IR] Replace of PointerType::getUnqual(Type) with opaque version (NFC) (#123909) 2025-01-23T09:23:05+00:00 Mats Jun Larsen mats@jun.codes 2025-01-23T09:23:05+00:00 d7c14c8f976fd291984e0c7eed75dd3331b1ed6d Follow up to https://github.com/llvm/llvm-project/issues/123569 
Follow up to https://github.com/llvm/llvm-project/issues/123569
 [IR] Remove unused variables from #123617 2025-01-20T16:47:38+00:00 Mats Larsen mats@jun.codes 2025-01-20T16:46:43+00:00 b95ed30ea2307dbcbe6199374c1e9a9b7a802ad0 Failed to notice them when landing that patch - apologies! 
Failed to notice them when landing that patch - apologies!
[IR] Replace of PointerType::get(Type) with opaque version (NFC) (#123617) 2025-01-20T15:32:56+00:00 Mats Jun Larsen mats@jun.codes 2025-01-20T15:32:56+00:00 416f1c465db62d829283f6902ef35e027e127aa7 In accordance with https://github.com/llvm/llvm-project/issues/123569 In order to keep the patch at reasonable size, this PR only covers for the llvm subproject, unittests excluded. 
In accordance with https://github.com/llvm/llvm-project/issues/123569

In order to keep the patch at reasonable size, this PR only covers for
the llvm subproject, unittests excluded.
 [SimplifyLibCall][Attribute] Fix bug where we may keep `range` attr with incompatible type (#112649) 2024-10-17T15:32:55+00:00 goldsteinn 35538541+goldsteinn@users.noreply.github.com 2024-10-17T15:32:55+00:00 c85611e8583e6392d56075ebdfa60893b6284813 In a variety of places we change the bitwidth of a parameter but don't update the attributes. The issue in this case is from the `range` attribute when inlining `__memset_chk`. `optimizeMemSetChk` will replace an `i32` with an `i8`, and if the `i32` had a `range` attr assosiated it will cause an error. Fixes #112633 
In a variety of places we change the bitwidth of a parameter but don't
update the attributes.

The issue in this case is from the `range` attribute when inlining
`__memset_chk`. `optimizeMemSetChk` will replace an `i32` with an
`i8`, and if the `i32` had a `range` attr assosiated it will cause an
error.

Fixes #112633
 [IRBuilder] Remove uses of CreateGlobalStringPtr() (NFC) 2024-09-23T14:30:50+00:00 Nikita Popov npopov@redhat.com 2024-09-23T14:20:09+00:00 ecb98f9fed65801d9ad2c138da7194496e18aeec Since the migration to opaque pointers, CreateGlobalStringPtr() is the same as CreateGlobalString(). Normalize to the latter. 
Since the migration to opaque pointers, CreateGlobalStringPtr()
is the same as CreateGlobalString(). Normalize to the latter.
[LLVM] Use {} instead of std::nullopt to initialize empty ArrayRef (#109133) 2024-09-19T15:16:38+00:00 Jay Foad jay.foad@amd.com 2024-09-19T15:16:38+00:00 e03f427196ec67a8a5cfbdd658f9eabe9bce83ce It is almost always simpler to use {} instead of std::nullopt to initialize an empty ArrayRef. This patch changes all occurrences I could find in LLVM itself. In future the ArrayRef(std::nullopt_t) constructor could be deprecated or removed. 
It is almost always simpler to use {} instead of std::nullopt to
initialize an empty ArrayRef. This patch changes all occurrences I could
find in LLVM itself. In future the ArrayRef(std::nullopt_t) constructor
could be deprecated or removed.