[SYCLomatic] Fix sycl to SYCLomatic pull down failed. #2143

CONFLICT (content): Merge conflict in clang/lib/CodeGen/CodeGenModule.cpp

…gRef). NFC

…s manager (#96378) Follows #95879.

This reverts commit 245491a ("[MC] Disable MCAssembler based constant folding for DwarfDebug") and cb09b5f ("[MC] Disable MCAssembler based constant folding for compact unwind and emitJumpTableEntry"). Checking the relative order of FA and FB is now faster due to de19f7b ("[MC] Replace fragment ilist with singly-linked lists").

…rguments (#96207) This commit simplifies the handling of dropped arguments and updates some dialect conversion documentation that is outdated. When converting a block signature, a `BlockTypeConversionRewrite` object and potentially multiple `ReplaceBlockArgRewrite` are created. During the "commit" phase, uses of the old block arguments are replaced with the new block arguments, but the old implementation was written in an inconsistent way: some block arguments were replaced in `BlockTypeConversionRewrite::commit` and some were replaced in `ReplaceBlockArgRewrite::commit`. The new `BlockTypeConversionRewrite::commit` implementation is much simpler and no longer modifies any IR; that is done only in `ReplaceBlockArgRewrite` now. The `ConvertedArgInfo` data structure is no longer needed. To that end, materializations of dropped arguments are now built in `applySignatureConversion` instead of `materializeLiveConversions`; the latter function no longer has to deal with dropped arguments. Other minor improvements: - Improve variable name: `origOutputType` -> `origArgType`. Add an assertion to check that this field is only used for argument materializations. - Add more comments to `applySignatureConversion`. Note: Error messages around failed materializations for dropped basic block arguments changed slightly. That is because those materializations are now built in `legalizeUnresolvedMaterialization` instead of `legalizeConvertedArgumentTypes`. This commit is in preparation of decoupling argument/source/target materializations from the dialect conversion.

The fadd_f64 test was in the middle of some f32 tests.

/llvm-project/clang-tools-extra/clangd/Format.cpp:284:11: error: no member named 'KeepEmptyLinesAtTheStartOfBlocks' in 'clang::format::FormatStyle' Style.KeepEmptyLinesAtTheStartOfBlocks = true; ~~~~~ ^ 1 error generated.

This is another relatively small adjustment to shuffleToIdentity, which has had a few knock-one effects to need a few more changes. It attempts to detect free concats, that will be legalized to multiple vector operations. For example if the lanes are '[a[0], a[1], b[0], b[1]]' and a and b are v2f64 under aarch64. In order to do this: - isFreeConcat detects whether the input has piece-wise identities from multiple inputs that can become a concat. - A tree of concat shuffles is created to concatenate the input values into a single vector. This is a little different to most other inputs as there are created from multiple values that are being combined together, and we cannot rely on the Lane0 insert location always being valid. - The insert location is changed to the original location instead of updating per item, which ensure it is valid due to the order that we visit and create items.

Add remove_if() method, similar to the one already present on SetVector. It is intended to replace the following pattern: for (Foo *Ptr : Set) if (Pred(Ptr)) Set.erase(Ptr); With: Set.remove_if(Pred); This pattern is commonly used for set intersection, where `Pred` is something like `!OtherSet.contains(Ptr)`. The implementation provided here is a bit more efficient than the naive loop, because it does not require looking up the bucket during the erase() operation again. However, my actual motivation for this is to have a way to perform this operation without relying on the current `std::set`-style guarantee that erase() does not invalidate iterators. I'd like to stop making use of tombstones in the small regime, which will make insertion operations a good bit more efficient. However, this will invalidate iterators during erase().

…ID from imported modules To support no-transitive-change model for named modules, we can't reuse type ID and identifier ID from imported modules arbitrarily. Since the theory for no-transitive-change model is, for a user of a named module, the user can only access the indirectly imported decls via the directly imported module. So that it is possible to control what matters to the users when writing the module. And it will be unsafe to do so if the users can reuse the type IDs and identifier IDs from the indirectly imported modules not via the directly imported modules. So in this patch, we don't reuse the type ID and identifier ID in the AST writer to avoid the problematic case.

We can't deref() them, so return false here.

runDFS() currently performs three hash table lookups. One in the main loop, one when checking whether a successor has already been visited and another when adding parent and reverse children to the successor. We can avoid the two additional lookups by making the parent number part of the stack, and then making the parent / reverse children update part of the main loop. The main loop already has a check for already visited nodes, so we don't have to check this in advance -- we can simply push the node to the worklist and skip it later.

mlir-config.h is included but not listed in dependencies

… (#95553) When running early-tailduplication we've seen problems with machine verifier errors due to register class mismatches after doing the machine SSA updates. Typical scenario is that there is a PHI node and another instruction that is using the same vreg: %othervreg:otherclass = PHI %vreg:origclass, %bb MInstr %vreg:origclass but then after TailDuplicator::tailDuplicateAndUpdate we get %othervreg:otherclass = PHI %vreg:origclass, %bb, ... MInstr %othervreg:otherclass Such rewrites are only valid if 'otherclass' is equal to (or a subclass of) 'origclass'. The solution here is based on adding a COPY instruction to make sure we satisfy constraints given by 'MInstr' in the example. So if 'otherclass' isn't equal to (or a subclass of) 'origclass' we insert a copy after the PHI like this: %othervreg:otherclass = PHI %vreg:origclass, %bb, ... %newvreg:origclass = COPY %othervreg:otherclass MInstr %newvreg:origclass A special case is when it is possible to constrain the register class instead of inserting a COPY. We currently prefer to constrain the register class instead of inserting a COPY, even if it is a bit unclear if that always is better (considering register pressure for the constrained class etc.). Fixes: llvm/llvm-project#62712

Change this function to be LLVM-style in name.

Syntacore SCR3 is a microcontroller-class processor core. Overview: https://syntacore.com/products/scr3 Co-authored-by: Dmitrii Petrov <[email protected]>

…IEs (#96484) If ParseStructureLikeDIE (or ParseEnum) encountered a declaration DIE, it would call FindDefinitionTypeForDIE. This returned a fully formed type, which it achieved by recursing back into ParseStructureLikeDIE with the definition DIE. This obscured the control flow and caused us to repeat some work (e.g. the UniqueDWARFASTTypeMap lookup), but it mostly worked until we tried to delay the definition search in #90663. After this patch, the two ParseStructureLikeDIE calls were no longer recursive, but rather the second call happened as a part of the CompleteType() call. This opened the door to inconsistencies, as the second ParseStructureLikeDIE call was not aware it was called to process a definition die for an existing type. To make that possible, this patch removes the recusive type resolution from this function, and leaves just the "find definition die" functionality. After finding the definition DIE, we just go back to the original ParseStructureLikeDIE call, and have it finish the parsing process with the new DIE. While this patch is motivated by the work on delaying the definition searching, I believe it is also useful on its own.

…#96514) This PR fixes llvm/llvm-project#96513. The way of creation of array type constant was incorrect: instead of creating [1, 1, 1] or [1, 1, 1, 1, 1, ....] constants, the same [1] constant was always created, substituting original composite constants. This in its turn led to a situation when only one of constants might exist in the code without emitting invalid code, the second constant would be eventually rewritten to the first constant, because a key to address both was an array of a single element (like [1]). This PR fixes the issue and purges from the code unneeded copy/pasted clone of the function that creates an array constant.

…nes (#95269) This patch extends #73964 and adds optimisation of load SVE intrinsics when predicate is zero.

The handling of `PointerType` is similar to `HeapType`. The only difference is that allocated flag is generated for `HeapType` and associated flag for `PointerType`. The tests for pointer to allocatable strings are disabled for now. I will enable them once #95906 is merged. The debugging in GDB looks like this: integer, pointer :: par2(:) integer, target, allocatable :: ar2(:) integer, target :: sc integer, pointer :: psc allocate(ar2(4)) par2 => ar2 psc => sc 19 par2 => ar2 (gdb) p par2 $3 = <not associated> (gdb) n 20 do i=1,5 (gdb) p par2 $4 = (0, 0, 0, 0) (gdb) ptype par2 type = integer (4) (gdb) p sc $5 = 3 (gdb) p psc $6 = (PTR TO -> ( integer )) 0x7fffffffda24 (gdb) p *psc $7 = 3

…ing for generic types (#89217) This patch is intended to be the first of a series with end goal to adapt atomic optimizer pass to support i64 and f64 operations (along with removing all unnecessary bitcasts). This legalizes 64 bit readlane, writelane and readfirstlane ops pre-ISel --------- Co-authored-by: vikramRH <[email protected]>

This change adds methods like buildGetFPEnv and similar for opcodes that represent manipulation on floating-point state.

This changes the behaviour in C++03 mode because we'll now use the builtin on Clang, but I don't think that's much of a problem.

This header used three-space indentation in a number of places. Reformat it completely.

This FIXME has already been addressed in #89358

Instead for iterating over all VFs when computing costs, simply iterate over the VFs available in the created VPlans. Split off from llvm/llvm-project#92555. This also prepares for moving the check if any vector instructions will be generated to be based on VPlan, to unblock recommitting llvm/llvm-project#92555.

Without the store, the vector loop body is empty. Add a store to avoid that, while not impacting the induction resume values that are created.

This patch implements lowering of the GlobalAddress, BlockAddress, JumpTable and BR_JT. Also patch adds legal support of the BR_CC operation for i32 type.

Some of these are just old, while others previously did not use UTC due to missing features that have since been implemented (such as signature matching).

These will be replaced later.

…Target` (#96500)

Since we mark the pseudos as mayLoad but do not provide any MMOs, isSafeToMove conservatively returns false, stopping MachineLICM from hoisting the instructions. PseudoLA_TLS_{LD,GD} does not actually expand to a load, so stop marking that as mayLoad to allow it to be hoisted, and for the others make sure to add MMOs during lowering to indicate they're GOT loads and thus can be freely moved.

… (#95061) This patch augments the HIPAMD driver to allow it to target AMDGCN flavoured SPIR-V compilation. It's mostly straightforward, as we re-use some of the existing SPIRV infra, however there are a few notable additions: - we introduce an `amdgcnspirv` offload arch, rather than relying on using `generic` (this is already fairly overloaded) or simply using `spirv` or `spirv64` (we'll want to use these to denote unflavoured SPIRV, once we bring up that capability) - initially it is won't be possible to mix-in SPIR-V and concrete AMDGPU targets, as it would require some relatively intrusive surgery in the HIPAMD Toolchain and the Driver to deal with two triples (`spirv64-amd-amdhsa` and `amdgcn-amd-amdhsa`, respectively) - in order to retain user provided compiler flags and have them available at JIT time, we rely on embedding the command line via `-fembed-bitcode=marker`, which the bitcode writer had previously not implemented for SPIRV; we only allow it conditionally for AMDGCN flavoured SPIRV, and it is handled correctly by the Translator (it ends up as a string literal) Once the SPIRV BE is no longer experimental we'll switch to using that rather than the translator. There's some additional work that'll come via a separate PR around correctly piping through AMDGCN's implementation of `printf`, for now we merely handle its flags correctly.

Extends llvm/llvm-project#95403 to handle non-constant cases - we can avoid unpacks/extensions from vXi8 to vXi16 by using PMADDUBSW instead and truncating the vXi16 results back together. Most targets benefit from performing this for non-constant cases - its just Intel Core/SandyBridge era CPUs that might experience additional Port0/15 contention (but lower instruction count). Fixes llvm/llvm-project#90748

This adds a new pattern that can legalize a multi-tile transfer_write as a single store loop. This is done as part of type decomposition as at this level we know each tile write is disjoint, but that information is lost after decomposition (without analysis to reconstruct it). Example (pseudo-MLIR): ``` vector.transfer_write %vector, %dest[%y, %x], %mask : vector<[16]x[8]xi16>, memref<?x?xi16> ``` Is rewritten to: ``` scf.for %slice_idx = %c0 to %c8_vscale step %c1 { %upper_slice_mask = vector.extract %mask[%slice_idx] ─┐ : vector<[8]xi1> from vector<[16]x[8]xi1> | %upper_slice = vector.extract %upper_tile[%slice_idx] |- Store upper tile : vector<[8]xi16> from vector<[8]x[8]xi16> | vector.transfer_write %upper_slice, | %dest[%slice_idx + %y, %x], %upper_slice_mask | : vector<[8]xi16>, memref<?x?xi16> ┘ %lower_slice_idx = %slice_idx + %c8_vscale ─┐ %lower_slice_mask = vector.extract %mask[%lower_slice_idx] | : vector<[8]xi1> from vector<[16]x[8]xi1> | %lower_slice = vector.extract %lower_tile[%slice_idx] |- Store lower : vector<[8]xi16> from vector<[8]x[8]xi16> | tile vector.transfer_write %lower_slice, | %dest[%lower_slice_idx + %y, %x], %lower_slice_mask | : vector<[8]xi16>, memref<?x?xi16> ┘ } ```

…(#95424) Summary: This patch adds `CMAKE_REQUIRED_FLAGS` for the GPU build so checks like `check_cxx_compiler_flags` work as expected. This is required because we need to hack around the potential lack of `nvlink` and `ptxas` for NVPTX targets and the fact that the AMDGPU target needs `-nogpulib` to avoid errors on lack of ROCm. This makes a few of the checks pass and also allows us to just check `-mcpu=native` for architecture detection instead of finding the tools manually.

Introduce a Loop::getLocStr stolen from LoopVectorize's static function getDebugLocString in order to have uniform debug output headers across LoopVectorize, LoopAccessAnalysis, and LoopDistribute. The motivation for this change is to have UpdateTestChecks recognize the headers and automatically generate CHECK lines for debug output, with minimal special-casing.

-1 mask elements are specified to return poison rather than undef nowadays , so update the reorderScalars() implementation to match.

The lowering of copyprivate clauses with allocatable or pointer variables was incorrect. This happened because the values passed to copyVar() are always wrapped in SymbolBox::Intrinsic, which resulted in allocatable/pointer variables being handled as regular ones. This is fixed by providing to copyVar() the attributes of the variables being copied, to make it possible to detect and handle allocatable/pointer variables correctly. Fixes #95801

I've not added any new tests for these, because the original conditions were wrong (they did not consider streaming mode) and we have tests for the positive cases.

And rename an argument to avoid an upper/lowercase clash.

Part of #93566.

…21)" This reverts commit 9267f8f. I changed a formatter option. I forgot to update other components that depend on the formatter when the option name changed.

This reverts commit 4c91b49 after 70cfece.

We should have been using __builtin_mul_overflow from the start instead of adding a manual (and error-prone) check for overflow. Fixes #96196

…er.store` (#94576) Depends on llvm/llvm-project#96313.

…on of i1 types (#95920) Previously isElementTypeLegalForScalableVector returned false for i1 types, which also prevented vectorisation of loops with i1 reductions. This is overkill - we only need to disable vectorisation for loads and/or stores of i1 types. I've added i1 as a legal type, but changed the cost model to return an invalid cost for loads and stores.

…rt (#96579) Address static verifier concerns about dead code in DoubleUnderscore check. Replace it with an assert.

This effort has quite a history: - This was first attempted in 2022 via bed3240, which broke std::shared_ptr<T const> and caused the change to be reverted in 9138666. - We then re-attempted landing the change in 276ca87 after fixing std::shared_ptr, but reports were made that this broke code en masse within Google. This led to the patch being reverted again in a54d028 with the goal to land this again with a migration path for vendors. This patch re-lands the removal while providing a migration path for vendors by providing the `_LIBCPP_ENABLE_REMOVED_ALLOCATOR_CONST` macro. This macro will be honored for the LLVM 19 release and will be removed after that, at which point allocator<const T> will be removed unconditionally. Fixes #73665

We have a fixed calling convention for stack pointer and frame pointer, we shouldn't try to shift anything around.

The actual size of scratch/private is determined at dispatch time, so add more plumbing to request it. Will be used in subsequent change.

Some of our custom expressions are not variadic and there seems to be little benefit in mentioning the variadic nature of expression nodes in the name anyway.

This paper was adopted at the Oct 2019 meeting in Ithaca, but the changes from the paper were later removed (editorially) by the C Floating Point study group due to being incorrect and unnecessary.

…639) When performing a load from uninitialized memory using !noundef, insert a non-terminator unreachable instruction, which will be converted to a proper unreachable by SimplifyCFG. This way we retain the fact that UB occurred on this code path.

Constants actual arguments in function/subroutine calls are currently lowered as allocas + store. This can sometimes inhibit LTO and the constant will not be propagated to the called function. Particularly in cases where the function/subroutine call happens inside a condition. This patch changes the lowering of these constant actual arguments to a global constant + fir.address_of_op. This lowering makes it easier for LTO to propagate the constant. The optimization must be enabled explicitly to run. Use -mmlir --enable-constant-argument-globalisation to enable. --------- Co-authored-by: Dmitriy Smirnov <[email protected]>

This adds order-modifier (reproducible|unconstrained) support to Order clause.

This commit adds basic types and definitions for NonSemantic.Shader.DebugInfo.100 standard for SPIRV. Full implementation of the standard will allow SPIRV backend to emit files with debug info included. Link to standard: https://github.com/KhronosGroup/SPIRV-Registry/blob/main/nonsemantic/NonSemantic.Shader.DebugInfo.100.html

This avoids different instantiations when the if and else types are different, resulting in reduced memory use by the compiler.

…odule (#91240) This PR addresses a problem that headers may not be able to be found if `#include` is used with std modules. Consider the following file: #include <boost/json.hpp> import std; int main(int, const char **) { } Boost will include something from libc++, but we are using -nostdinc++ at [1] so the compiler can not find any default std header. Therefore the locally built header needs to be public. [1]: https://github.com/RichardLuo0/llvm-project/blob/15fdd47c4b110b64dc61f636e42e0484bf8bdbe0/libcxx/modules/CMakeLists.txt.in#L52

Created using spr 1.3.4

This reverts commit 020f69c.

There is code duplication in all containers that static_assert the allocator matches the allocator requirements in the spec. This check can be moved into a more centralised place.

Sometime tsan runtimes calls, like `__tsan_mutex_create ()`, need to store a stack in the StackDepot, and the Depot may need to start and maintenance thread. Example: ``` __sanitizer::FutexWait () __sanitizer::Semaphore::Wait () __sanitizer::Mutex::Lock () __tsan::SlotLock () __tsan::SlotLocker::SlotLocker () __tsan::Acquire () __tsan::CallUserSignalHandler () __tsan::ProcessPendingSignalsImpl () __tsan::ProcessPendingSignals () __tsan::ScopedInterceptor::~ScopedInterceptor () ___interceptor_mmap () pthread_create () __sanitizer::internal_start_thread () __sanitizer::(anonymous namespace)::CompressThread::NewWorkNotify () __sanitizer::StackDepotNode::store () __sanitizer::StackDepotBase<__sanitizer::StackDepotNode, 1, 20>::Put () __tsan::CurrentStackId () __tsan::MutexCreate () __tsan_mutex_create () ``` pthread_create() implementation may hit other interceptors recursively, which may invoke ProcessPendingSignals, which deadlocks. Alternative solution could be block interceptors closer to TSAN runtime API function, like `__tsan_mutex_create`, or just before `StackDepotPut``, but it's not needed for most calls, only when new thread is created using `real_pthread_create`. I don't see a reasonable way to create a regression test.

…. (#96582)

… (#95224) To enable function multi-versioning (FMV), current checks which rely on cmd line options or global macros to see if target feature is present need to be removed. This patch removes those for NEON and also implements changes to NEON header file as proposed in [ACLE](ARM-software/acle#321).

This patch implements an improvement introduced in P3029R1 that was missed in #87873. It adds a deduction of static extents if integral_constant-like constants are passed to `std::extents`.

This reverts commit bb5ab1f.

The GCC build has gotten to the point where it's often hard to find the actual error in the build log. We should look into enabling these warnings again in the future, but it looks like a lot of them are bogous.

The builtin causes the program to stop its execution abnormally and shows a human-readable description of the reason for the termination when a debugger is attached or in a symbolicated crash log. The motivation for the builtin is explained in the following RFC: https://discourse.llvm.org/t/rfc-adding-builtin-verbose-trap-string-literal/75845 clang's CodeGen lowers the builtin to `llvm.trap` and emits debugging information that represents an artificial inline frame whose name encodes the category and reason strings passed to the builtin.

Mark LWG3382 as "Nothing To Do" and add tests.

Annoyingly gfx90a/940 support this for global/flat but not buffer.

New fixes: - properly init the `std::optional<std::vector>` to an empty vector as opposed to `{}` (which was effectively `std::nullopt`). --------- Co-authored-by: Vy Nguyen <[email protected]>

https://github.com/ARM-software/abi-aa/blob/main/aapcs32/aapcs32.rst#6212stack-constraints-at-a-public-interface mentions that the stack on ARM32 is double word aligned. Remove confused comments around ArgcType. argc is always an int, passed on the stack, so we need to store a pointer to it (regardless of ILP32 or LP64).

Alastair Robertson reported a huge compilation time increase without -g for bpf target when comparing to x86 ([1]). In my setup, with '-O0', for x86, a large basic block compilation takes 0.19s while bpf target takes 2.46s. The top function which contributes to the compile time is eliminateFrameIndex(). Such long compilation time without -g is caused by commit 05de2e4 ("[bpf] error when BPF stack size exceeds 512 bytes") The compiler tries to get some debug loc by iterating all insns in the basic block which will be used when compiler warns larger-than-512 stack size. Even without -g, such iterating also happens which cause unnecessary compile time increase. To fix the issue, let us move the related code when the compiler is about to warn stack limit violation. This fixed the compile time regression, and on my system, the compile time is reduced from 2.46s to 0.35s. [1] bpftrace/bpftrace#3257 Co-authored-by: Yonghong Song <[email protected]>

…. (#96593) Many state of the art models and quantization operations are now directly working on vector.contract on integers. This commit enables generalizes ext-contraction folding S.T we can emit more performant vector.contracts on codegen pipelines. Signed-off-by: Stanley Winata <[email protected]>

The `getDroppedDims` utility function does not follow the convention of dropping outermost unit dimensions first when inferring a rank reduction mask for a slice. This PR updates the implementation to match this convention.

N2843 was subsumed by N2882; we could probably consider removing subsumed entries, but I've been leaving them to help folks looking at the editor's report from various working drafts and wondering about the changes.

…lang (#96555) Updates the install path for clang-doc to share/clang-doc instead share/clang to avoid confusion

Removes stdexecpt from clang-doc test introduced in llvm/llvm-project#93928 since it violates the rule that test must be freestanding

We use REAL() calls in interceptors, but DEFINE_REAL_PTHREAD_FUNCTIONS has nothing to do with them and only used for internal maintenance threads. This is done to avoid confusion like in #96456.

Co-authored-by: Alexey Bataev <[email protected]>

…91327)

This paper only matters for TS18661-3 integration.

According to https://reviews.llvm.org/D114250 this was to handle Mac specific issue, however the test is Linux only. The test effectively prevents to lock main allocator on fork, but we do that on Linux for other sanitizers for years, and need to do the same for TSAN to avoid deadlocks.

r7 is reserved in thumb2 (typically for the frame pointer, as opposed to r11 in ARM mode), so assigning to a variable with explicit register storage in r7 will produce an error. But r7 is where the Linux kernel expects the syscall number to be placed. We can use a temporary to get the register allocator to pick a temporary, which we save+restore the previous value of r7 in. Fixes: #93738

These functions used only for `fork`. Unused parameter `child` will be used in followup patches.

Cap the alignment to 128 bytes as that is the maximum alignment supported by PTX. The restriction is mentioned in the parameter passing section (Note D) of the [PTX Writer's Guide to Interoperability] (https://docs.nvidia.com/cuda/ptx-writers-guide-to-interoperability/index.html#parameter-passing) > D. The alignment must be 1, 2, 4, 8, 16, 32, 64, or 128 bytes.

Reland: llvm/llvm-project#95456 This patch improves the ROCDL gpu serialization API by: - Introducing the enum `AMDGCNLibraries` for specifying the AMD GCN device code libraries to use during linking. - Removing `getCommonBitcodeLibs` in favor of `AMDGCNLibraries`. Previously `getCommonBitcodeLibs` would try to load all AMD GCN bitcode librariesm now it will only load the requested libraries. - Exposing the `compileToBinary` method and making it virtual, allowing downstream users to re-use this method. - Exposing `moduleToObjectImpl`, this method provides a prototype flow for compiling to binary, allowing downstream users to re-use this method. - It also avoids constructing the control variables if no device libraries are being used. - Changes the style of the error messages to be composable, ie no full stops. - Adds an error message for when the ROCm toolkit can't be found but it was required.

We do that for other Sanitizers, and we should do the same for TSAN. There are know deadlocks reports here.

This reduces codesize. As discussed in #92707.

… (#95180) These instructions can be generated using regular LL intrinsics. Specified at: https://github.com/WebAssembly/half-precision/blob/29a9b9462c9285d4ccc1a5dc39214ddfd1892658/proposals/half-precision/Overview.md

This PR adds -mtune as a valid flang flag and passes the information through to LLVM IR as an attribute on all functions. No specific architecture optimizations are added at this time.

This paper was a rewording of WG14 N1485, correcting terminology and bringing the C11 feature slightly closer in line with the C++11 feature. There is nothing additional to be done or test to conform to what was specified by WG14 N1537, so we'll remove the entry and lean on N1485 to track status for atomics.

Found while skimming this code. Don't have a reproducible test case for this but the nullptr check should clearly occur before we try to dereference `location_sp`.

Summary: The StringError class has a specialized method that creates the inconvertible error code for you. It's much easier to read this way.

This reverts commit 05d167f. Reverting the patch fixes the following under EXPENSIVE_CHECKS: LLVM :: CodeGen/AMDGPU/sched-group-barrier-pipeline-solver.mir LLVM :: CodeGen/AMDGPU/sched-group-barrier-pre-RA.mir LLVM :: CodeGen/PowerPC/aix-xcoff-used-with-stringpool.ll LLVM :: CodeGen/PowerPC/merge-string-used-by-metadata.mir LLVM :: CodeGen/PowerPC/mergeable-string-pool-large.ll LLVM :: CodeGen/PowerPC/mergeable-string-pool-pass-only.mir LLVM :: CodeGen/PowerPC/mergeable-string-pool.ll

…e target link (#91829) This PR attempts to fix common block mapping for regular mapping of these types as well as when they have been marked as "declare target link". This PR should allow correct mapping of both the members of a common block and the full common block via its block symbol. The main changes were some adjustments to the Fortran OpenMP lowering to HLFIR/FIR, the lowering of the LLVM+OpenMP dialect to LLVM-IR and adjustments to the way the we handle target kernel map argument rebinding inside of the OMPIRBuilder. For the Fortran OpenMP lowering were two changes, one to prevent the implicit capture of common block members when the common block symbol itself has been marked and the other creates intermediate member access inside of the target region to be used in-place of those external to the target region, this prevents external usages breaking the IsolatedFromAbove pact. In the latter case, there was an adjustment to the size calculation for types to better handle cases where we pass an array as the type of a map (as opposed to the bounds and the type of the element), which occurs in the case of common blocks. There is also some adjustment to how handleDeclareTargetMapVar handles renaming of declare target symbols in the module to the reference pointer, now it will only apply to those within the kernel that is currently being generated and we also perform a modification to replace constants with instructions as necessary as we cannot replace these with our reference pointer (non-constant and constants do not mix nicely). In the case of the OpenMPIRBuilder some changes were made to defer global symbol rebinding to kernel arguments until all other arguments have been rebound. This makes sure we do not replace uses that may refer to the global (e.g. a GEP) but are themselves actually a separate argument that needs bound. Currently "declare target to" still needs some work, but this may be the case for all types in conjunction with "declare target to" at the moment.

…(#96537) There are multiple ways to define a remainder operation. Depending on the definition, the result could be either always positive or have the sign of the dividend. The pattern lowering `arith.remf` to LLVM assumes that the semantics match `llvm.frem`, which seems to be reasonable. The folder, however, is implemented via `APFloat::remainder()` which has different semantics. This patch matches the folding behaviour to lowering behavior by using `APFloat::mod()`, which matches the behavior of `llvm.frem` and libm's `fmod()`. It also updates the documentation of `arith.remf` to explain this behavior: The sign of the result of the remainder operation always matches the sign of the dividend (LHS operand). frem documentation: https://llvm.org/docs/LangRef.html#frem-instruction Fix llvm/llvm-project#94431 --------- Co-authored-by: Jakub Kuderski <[email protected]>

This PR XFAILS `llvm/test/DebugInfo/attr-btf_type_tag.ll` on AIX since we we don’t have `.debug_addr` section. Co-authored-by: Nivetha Kuruparan <[email protected]>

Describe steps for optimizing the Linux kernel with BOLT.

Reverts llvm/llvm-project#95043

…457) The test clang/test/Preprocessor/embed_weird.cpp creates a file directly in the Inputs dir in the llvm-project repo instead of the temporary directory. The llvm-project repo may be write protected e.g. in a sandboxed environment. This patch creates a separate temporary directory where the null_byte.bin file is created along with the rest of copies of the other embed-files needed for the testcase.

CONFLICT (content): Merge conflict in llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp

…rnate node, NFC.

…lly` (#96585) AvailableExternally linkage is interesting because, in ThinLTO cases, it means the function may get elided if it survives inlining - see `elim-avail-extern` pass.

…al variable" case On ELF platforms, the instrumentation registers global variables using `__asan_register_elf_globals` for the default `UseGlobalsGC` case. If all instrumented global variables in a module are discarded by linker GC, we will have `start == stop`. Normally `start == 0`, but `start != 0` is possible with a linker script retaining `asan_globals`. The called `__asan_register_globals` would access out-of-bounds `globals[n-1]`, though there is likely no runtime failure. Pull Request: llvm/llvm-project#96529

The VReg2SUnitMap type is not used anywhere (it has probably been obsolete since commit 97d0ffb back in 2015). This commit simply removes the type definition.

…ns (#90461) This pull request will change the merging of ``debug_str_offset`` to merge per contribution and correctly copy over each contribution header to the merged section. I have added some test data which is in dwarf5 format as this is where the section contribution header was introduced, as far as i can tell.

If the base node is signed, but some values are unsigned, still the whole node should be considered signed. Also, an extra bitwidth analysis should be performed, when estimating the minimal bitwidth.

Adds support in MIR parser for parsing bfloat immediates, and adds a test for this.

…rounding modes. (#96591) Sharing the same algorithm as double precision sin: llvm/llvm-project#95736

13a79bb (2017) unified `BeginSymbol` and section symbol for ELF. This patch does the same for COFF. * In getCOFFSection, all sections now have a `BeginSymbol` (section symbol). We do not need a dummy symbol name when `getBeginSymbol` is needed (used by AsmParser::Run and DWARF generation). * Section symbols are in the global symbol table. `call .text` will reference the section symbol instead of an undefined symbol. This matches GNU assembler. Unlike GNU, redefining the section symbol will cause a "symbol 'foo0' is already defined" error (see `section-sym-err.s`). Pull Request: llvm/llvm-project#96459

…or sequence. If the vectorized scalar is not the insert value in the buildvector sequence but the index, it should be always extracted.

Fixes #92554 (std::reverse will auto-vectorize now) When calculating number of times a exit condition containing a comparison is executed, we mostly assume that RHS of comparison should be loop invariant, but it may be another add-recurrence. ~In that case, we can try the computation with `LHS = LHS - RHS` and `RHS = 0`.~ (It is not valid unless proven that it doesn't wrap) **Edit:** We can calculate back edge count for loop structure like: ```cpp left = left_start right = right_start while(left < right){ // ...do something... left += s1; // the stride of left is s1 (> 0) right -= s2; // the stride of right is -s2 (s2 > 0) } // left and right converge somewhere in the middle of their start values ``` We can calculate the backedge-count as ceil((End - left_start) /u (s1- (-s2)) where, End = max(left_start, right_start). **Alive2**: https://alive2.llvm.org/ce/z/ggxx58

Currently TableGen does not directly detect duplicate synthesized registers as can happen in this example: def GPR128 : RegisterTuples<[sub0, sub1, sub2, sub3], [(decimate (shl GPR32, 0), 1), (decimate (shl GPR32, 1), 1), (decimate (shl GPR32, 2), 1), (decimate (shl GPR32, 3), 1)]>; def GPR128_Aligned : RegisterTuples<[sub0, sub1, sub2, sub3], [(decimate (shl GPR32, 0), 4), (decimate (shl GPR32, 1), 4), (decimate (shl GPR32, 2), 4), (decimate (shl GPR32, 3), 4)]>; TableGen does fail, but with an unrelated and difficult to understand error that happens downstream of tuple expansion: "error: No SubRegIndex for R0_R1_R2_R3 in R0_R1_R2_R3". This patch detects the problem directly during expansion and emits an error pointing the user to the actual issue: "error: Register tuple redefines register 'R0_R1_R2_R3'".

Cover amdgpu.no.fine.grained.memory vs. amdgpu.no.remote.memory.

The opaque type jmp_buf should only be tested in fullbuild mode.

If only bits 8, 16, 24, 32, etc. can be non-zero. This is what (mul X, 255) is decomposed to. This decomposition happens early before RISC-V DAG combine runs. This patch does not support types larger than XLen so i64 on rv32 fails to generate 2 orc.b instructions. It might have worked if the mul hadn't been decomposed before it was expanded. Partial fix for #96595.

They implements IEEE754-2019 minimumNumber and maximumNumber semantics. Newer libc also has these 2 functions with names fminimum_num fmaximum_num We are planning add minimumnum and maximumnum intrinsic. This is a step to the goal.

Add ConstantRangeList::unionWith() and ::intersectWith(). These methods will be used in the "initializes" attribute inference. llvm/llvm-project@df11106

CONFLICT (content): Merge conflict in clang/test/Driver/sycl-linker-wrapper-image.cpp

CONFLICT (content): Merge conflict in clang/lib/Driver/Driver.cpp CONFLICT (content): Merge conflict in clang/lib/Driver/ToolChains/HIPAMD.cpp

…581) The PR removes the `*` from the generic MLIR Vector/Linalg rules. The `*` symbol keeps the match local to the files in the directory, excluding sub-directories, which was not the intention when I added these rules.

…le (#96594)

Fixes assert seen trying to use default number of inlined elements for `SmallVector<T>` but `sizeof(T)` is really big. Seen with -DLLVM_ENABLE_EXPENSIVE_CHECKS.

…scheduler (#96288) Added some logic to check loop-carried phis in the window scheduler. It now includes the scenario where the preceding phi uses the virtual register defined by the succeeding phi.

JITDylib::removeTracker already runs with the session mutex locked (and must do so), so remove the redundant locking and add an 'IL_' ("inside lock") prefix to the method name.

@Sahil123

This fixes a bug in ObjectLinkingLayer::computeBlockNonLocalDeps: The worklist needs to be built *after* all immediate dependencies / dependants are recorded, rather than trying to populate it as part of the same loop. (Trying to do the latter causes us to miss some blocks that should have been included in the worklist). This fixes a bug discovered by @Sahil123 on discord during work on out-of-process execution support in the clang-repl. No testcase yet. This *might* be testable with a unit test and a custom JITLinkContext but I believe some aspects of the algorithm depend on memory layout. I'll need to investigate that. Alternatively we could add llvm-jitlink testcases that exercise concurrent linking (and should probably do that anyway). Either option will require some investment and I don't want to hold this fix up in the mean time.

This also introduces "Test and conditional Read-Modify-Write". The flow to `atomicrmw or` is marked as `unlikely`.

`IsRela` is used by lld to differentiate REL and RELA static relocations. The proposed CREL patch will reuse `IsRela` for CREL (#91280). Rename `IsRela` to be more appropriate. Pull Request: llvm/llvm-project#96592

It should be a typo when the author created this file from X86OptimizeLEAs.cpp.

This reverts commit 174d353. It introduced new typo "IMul" by accident.

It should be a typo when the author created this file from X86OptimizeLEAs.cpp.

…d via createWithDefaultAttr(). Functions created with createWithDefaultAttr() need to have the correct target-{cpu,features} attributes to avoid miscompilations such as using the wrong relocation type to access globals (missing tagged-globals feature), clobbering registers specified via -ffixed-* (missing reserve-* feature), and so on. There's already a number of attributes copied from the module flags onto functions created by createWithDefaultAttr(). I don't think module flags are the right choice for the target attributes because we don't need the conflict resolution logic between modules with different target attributes, nor does it seem sensible to add it: there's no unambiguously "correct" set of target attributes when merging two modules with different attributes, and nor should there be; it's perfectly valid for two modules to be compiled with different target attributes, that's the whole reason why they are per-function. This also implies that it's unnecessary to serialize the attributes in bitcode, which implies that they shouldn't be stored on the module. We can also observe that for the most part, createWithDefaultAttr() is called from compiler passes such as sanitizers, coverage and profiling passes that are part of the compile time pipeline, not the LTO pipeline. This hints at a solution: we need to store the attributes in a non-serialized location associated with the ambient compilation context. Therefore in this patch I elected to store the attributes on the LLVMContext. There are calls to createWithDefaultAttr() in the NVPTX and AMDGPU backends, and those calls would happen at LTO time. For those callers, the bug still potentially exists and it would be necessary to refactor them to create the functions at compile time if this issue is relevant on those platforms. Fixes #93633. Reviewers: fmayer, MaskRay, eugenis Reviewed By: MaskRay Pull Request: llvm/llvm-project#96721

@premanandrao

Test needs update after cbf6e93 2024-05-28 [clang codegen] Delete unnecessary GEP cleanup code. (#90303). Change made by @premanandrao

…cl (#14295) clang-cl -O2/-Ot now implies -O3, update test to match

…14277) The failure was a result of 255986e [Driver] BuildOffloadingActions: Stabilize iteration order.

Signed-off-by: Isha Agarwal <[email protected]>

…rained.tan intrinsics with fp-accuracy. (#14193) This fixes the following LIT tests: * clang/test/CodeGen/fp-accuracy.c * clang/test/CodeGenSYCL/fp-accuracy.cpp * sycl/test/optional_kernel_features/fp-accuracy.c * sycl/test/optional_kernel_features/fp-accuracy.cpp.

CONFLICT (content): Merge conflict in clang/lib/CodeGen/CodeGenAction.cpp CONFLICT (content): Merge conflict in llvm/lib/IR/LLVMContext.cpp

Update a test after llvm-project commit d10b765 ("[ConstantFold] Remove notional over-indexing fold (#93697)", 2024-05-30). Original commit: KhronosGroup/SPIRV-LLVM-Translator@935848c97506a46

Some of the upstream PRs are getting backported to the llvm_release_* branches, but those changes are never released. That prevents them from distributing as precompiled packages in various distributions like conda-forge and others. This PR targets this issue by creating automated workflow that is triggered once a month and generates automated releases for each such branch if there were changes since last release. This PR Adds workflow to generate releases every month from llvm_release_* branches in the format %llvm_major%.%llvm_minor%.%latest patch version +1%. For example: v18.1.1 v17.0.2 v17.0.1 v14.0.1 etc Release description matches as close as possible to current releases. The only difference is that llvm versions is represented by two numbers, instead of three, because it is impossible to recover exact version. You can check out example of generated versions here (there are few releases from the original proposal): https://github.com/ZzEeKkAa/SPIRV-LLVM-Translator/releases Workflow is set to be triggered once a month. It is also possible to trigger it manually from github actions UI. Merge process Merge the PR to main Trigger workflow manually Note There is no need to backport changes to all branches, since workflow dispatch on schedule basis can be performed only from main branch. Fixes: oneapi-src#1898 Fixes: oneapi-src#1508 Original commit: KhronosGroup/SPIRV-LLVM-Translator@63e89a9a268e5c2

…#2504) Round up number of elements in a Vector to a power of 2 when calculating memory size. Memory size will be calculated as BaseType * bit_ceil(ComponentCount). The previous calculation already rounded 3 elements to 4 elements. Signed-off-by: Lu, John <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@a6398f45674bb5d

Signed-off-by: Sidorov, Dmitry <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@7d6d66975ff394a

bit_ceil requires C++20. Use llvm::bit_ceil to avoid this requirement. Signed-off-by: Lu, John <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@aab92ecc22e2f1e

The test performed a read_image operation on an image declared `write_only`. `spirv-val` recently started flagging this. Update the image access attribute to "read-only" (i.e., 0). Fixes KhronosGroup/SPIRV-LLVM-Translator#2597 Original commit: KhronosGroup/SPIRV-LLVM-Translator@bd0fffe337d27b3

…2599) In this case zero GEP will be created a single time, all the decorations will be attached to it. Signed-off-by: Sidorov, Dmitry <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@9aa3c9c12f51775

Required after llvm/llvm-project@dc726c340392d: Reapply#4 "[RemoveDIs] Load into new debug info format by default in LLVM Signed-off-by: Sidorov, Dmitry <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@338a37ef59ded4f

Make code clearer and check for exact number of operands. Signed-off-by: Lu, John <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@cd4eaf69744a413

The affected source files were relying on transitive includes that were no longer included after recent llvm-project changes (such as 36c6632 ("[IR] Don't include PassInstrumentation.h in PassManager.h (NFC) (#96219)", 2024-06-21)). Original commit: KhronosGroup/SPIRV-LLVM-Translator@97069a601d2e733

... when test expects x86_64-specific results. Original commit: KhronosGroup/SPIRV-LLVM-Translator@681f027524840ff

It was implemented via new decoration, which is not correct. Instead it should be Function Parameter Attribute decoration. In this commit starts fixing this in step-by-step manner. Signed-off-by: Sidorov, Dmitry <[email protected]> Co-authored-by: Maksimova, Viktoria <[email protected]> Original commit: KhronosGroup/SPIRV-LLVM-Translator@0db0f98bfab5b25

…same (#2528) Original commit: KhronosGroup/SPIRV-LLVM-Translator@4a6a1746c61f917

Update a check pattern in a test after llvm-project commit 04c2785 ("[MC,COFF] Change how we handle section symbols", 2024-06-25). Original commit: KhronosGroup/SPIRV-LLVM-Translator@277654e5b16a47a

When there is forward declaration of a spirv entry, its decorates are not translated until its definition is seen. Forward id is re-used for its entry. Id in entry decorates should use forward id as well. Original commit: KhronosGroup/SPIRV-LLVM-Translator@305f48884606abf

Calls to llvm.debug.value were changed to debug_value with different syntax

Will also be in sycl branch through pulldown in intel/llvm#14327 --------- Co-authored-by: sys_ce_bb <[email protected]> Co-authored-by: premanandrao <[email protected]>

…n into IR-based analysis (#14220) Based on feedback from intel/llvm#14197, I seperated out the code that generates the module properties and symbol table into separate functions that can be called by anyone, and just looks at the IR and entry points. For now, we still call it inside `sycl-post-link` because we still support the old offloading model, but once we drop support for that we can drop this responsibility from sycl-post-link and only compute it inside `clang-linker-wrapper`, both for normal compilation and thinLTO. In a (hopefully soon) future PR I plan to call these functions from `clang-linker-wrapper` when compiling for thinLTO, which we need because we will split early. Most of this change should be NFC(I). The expected changes are: 1) New option to sycl-post-link to generate the properties file 2) Driver change to NOT pass the option from 1) in thinLTO mode 3) Two minor chages in logic from properties generation, I've called these out inline. --------- Signed-off-by: Sarnie, Nick <[email protected]>

The PassInstrumentationAnalysis class was moved to PassInstrumentation.h, requiring an additional header include.

…name

The names of classes is now emitted fully qualified, so test expected errors needed to adjust

Reusing prefix SPIRV64 while adding an useless(and wrong) line AMDGPUSPIRV64 is confusing. Update it by copying SPIRV64 line to AMDGPU line.

pre-commit PR for oneapi-src/unified-runtime#1696 --------- Signed-off-by: Neil R. Spruit <[email protected]> Co-authored-by: Kenneth Benzie (Benie) <[email protected]>

This commit implements the sycl_oneapi_raw_kernel_arg extension. --------- Signed-off-by: Larsen, Steffen <[email protected]>

Adds API entries and descriptions for the whole graph update feature, which allows updating an executable `command_graph` using another modifiable graph with the same topology. This provides a cleaner alternative to individual node update, especially when using graph recording or updating a large number of parameters. The PR also includes a small usage example. --------- Co-authored-by: Ben Tracy <[email protected]> Co-authored-by: Ewan Crawford <[email protected]>

intel/llvm#14376 tracked in intel/llvm#14387 The two fail tests will XPASS here because I haven't merged the driver change, I will do it immediately after this PR is merged ``` Failed Tests (2): SYCL :: Basic/image/srgba-read.cpp SYCL :: syclcompat/launch/launch.cpp ``` Signed-off-by: Sarnie, Nick <[email protected]>

…(#13497)

Not part of SYCL 2020. Wider used exception subclasses will be removed in individual PRs to ease review.

Conflicts: llvm/include/llvm/Passes/CodeGenPassBuilder.h

… supported by clang-cl (#14348) Co-authored-by: Arvind Sudarsanam <[email protected]>

…4247) Fix command line argument passed to "spirv-to-ir-wrapper" invocation in clang-linker-wrapper. Also make clang-linker-wrapper print arguments quoted if needed.

It was removed in SYCL 2020 and should be dropped during the current ABI breaking window. We still need to access PI error code, either for internal needs or for the backend interoperability, so the member field remains. Also, introduce `sycl::detail::get_pi_error(const exception &)` instead for internal needs (cache cleanup when out of resources only currently).

uninitialized value causing complaint from c.v.

This changes the accuracy declared for 'ha' SVML functions to 1.0, reflecting the actual standard used by the library team for these functions.

…removal (#14396) Signed-off-by: Tikhomirova, Kseniya <[email protected]>

Scheduled drivers uplift Co-authored-by: GitHub Actions <[email protected]>

…#14406) SYCL 1.2 exception classes don't use `context` argument so it can be removed. `online_compile_error` was the single user of an overload, so I've removed it and change the ctor used by it. --------- Co-authored-by: Alexey Bader <[email protected]>

With -support-dynamic-linking, non SYCL_EXTERNAL functions are internalized. --------- Signed-off-by: Lu, John <[email protected]>

…PIROrSPIRV()" in AddressSanitizer.cpp (#14413) SYCL is going to switch to SPIR-V backend soon, this PR changed "TargetTriple.isSPIR()" to "TargetTriple.isSPIROrSPIRV()" to improve compatibility

…3830) Currently building Native CPU with shared libraries enabled leads to a CMake error when configuring: some components of the oneAPI Construction Kit depend on `LLVMPasses`, and since they are also added as `link_libraries` to `SYCLLowerIR` (which `LLVMPasses` depends on), that creates a circular dependency that is not allowed when building with shared libraries enabled. This PR addresses this by moving all the Native CPU components to a new folder (`SYCLNativeCPUUtils`), that is not linked to `LLVMPasses`, thus breaking the circular dependencies.

The sycl/test-e2e/syclcompat/launch/launch.cpp test was marked XFAIL but seems to be passing in post-commit. This commit changes in to UNSUPPORTED. Signed-off-by: Larsen, Steffen <[email protected]>

This uses the TargetLowering getSimpleValueType mechanism to retrieve the ValueType info inside the X86 cost model. This resolves a build issue we were seeing for the miniQMC application after llvm/llvm-project#92671.

…e (#14418) While the PTX directive is "minnctapersm", the NVVM annotation is "minctasm". This can be seen in the NVPTX backend, and in the NVVM IR spec, section 13.3.

Moving a temporary variable prevents copy ellision, and by default produces a compiler warning. This PR also fixes up the naming of a few nearby variables to better conform with LLVM (and the surrounding code).

…lkan device (#14386) The incorrect vulkan device can be selected when both Intel and Nvidia devices are available on the same system. Change tests to use the same device as SYCL default to.

Declaring upfront that `reqd_work_group_size` has the same semantics between OpenCL and SYCL is misleading because the dimensionality is different. The docs for `work_group_size_hint` were better in clarifying the difference, so those have been copied and adapted. Describe OpenCL upfront as it's simpler, and won't be buried by the wordier SYCL documentation. Try and re-enforce the SYCL dimensionality rules to aid people more familiar with OpenCL and other similar languages. Clarify that the `max_work_group_size` attribute (at least currently) behaves like `reqd_work_group_size` but we require *all* dimensions to be supplied.

Updates the git tag used to fetch the oneAPI Construction Kit.

NVVM IR supports separated maxntidx, maxntidy, and maxntidz annotations. The backend will print them individually as three dimensions. This better preserves programmer intent than prematurely flattening them together. Note that the semantics are in fact identical; the CUDA implementation internally multiplies all dimensions together and only guarantees that the total is never exceeded, but not that any individual dimension is not exceeded. Thus 64,1,1 is identical to 4,4,4. We try and preserve a logical mapping of dimensions by index flipping between SYCL (z,y,x) and NVVM (x,y,z) in CUDA terminology despite, as mentioned above, it being largely irrelevant. Also this patch simplifies the attribute's getter functions as all dimensions are mandatory, and the getters seemed copied from the reqd_work_group_size attribute where some are optional. We could probably improve the code further by making the operands "unsigned" and not "Expr", and renaming them from X,Y,Z to Dim{0,1,2} as per the SYCL spec. This has been left for future work, however, as there's a non-trivial amount of code that expects to be able to treat the max_work_group_size and reqd_work_group_size attributes identically through templates and identical helper methods.

…lated handler ctor param (#14258) Host device support is deprecated long time ago. Removes: 1) is_host() API deprecated long time ago, SYCL2020 deprecations group. 2) remove isHost ctor param and corresponding field from handler class. Handler instance is always created by RT. User deals with handler instance by creating kernel lambda which accepts handler as parameter and then calls methods of handler. --------- Signed-off-by: Tikhomirova, Kseniya <[email protected]>

… (#14440) Fixes the path for `x <= 2` in `int_as_queue_ptr`, which was returning an address to a temporary pointer. Signed-off-by: Alberto Cabrera <[email protected]>

Pulls in changes from oneapi-src/unified-runtime#1212 --------- Co-authored-by: Kenneth Benzie (Benie) <[email protected]>

This patch intended to be an improvement for composite device implementation code coverage, but it turned out that it also helped to find a bug in the implementaiton.

Signed-off-by: Tikhomirova, Kseniya <[email protected]>

Does scheduler cleanup explicitly. Windows path has some "cut" code in prepareSchedulerForRelease (due to shutdown features) that makes this function useless for UT PiMock cleanup. fixes intel/llvm#13457 Signed-off-by: Tikhomirova, Kseniya <[email protected]>

pre-commit PR for oneapi-src/unified-runtime#1802 --------- Signed-off-by: Neil R. Spruit <[email protected]> Co-authored-by: Kenneth Benzie (Benie) <[email protected]> Co-authored-by: Aaron Greig <[email protected]>

The class was originally an implementation of the SYCL 1.2.1 program class, and then used internally for the kernel bundle implementation. It shouldn't be needed anymore.

Changed the `queue.fill()` implementation to make use of the native functions for a specific backend. Also, unified the implementation with the one for memset, since it is just an 8-bit subset operation of fill. In the CUDA case, both memset and fill are currently calling `urEnqueueUSMFill` which depending on the size of the filling pattern calls either `cuMemsetD8Async`, `cuMemsetD16Async`, `cuMemsetD32Async` or `commonMemSetLargePattern`. Before this patch memset was using the same thing, just beforehand setting patternSize always to 1 byte which resulted in calling `cuMemsetD8Async`. In other backends, the behaviour is analogous. The fill method was just invoking a `parallel_for` to fill the memory with the pattern which was making this operation quite slow.

This PR removes the SYCL 2017 deprecated tests as a continuation of intel/llvm#14239 in preparation to land intel/llvm#13411

Bumps [certifi](https://github.com/certifi/python-certifi) from 2024.2.2 to 2024.7.4. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/certifi/python-certifi/commit/bd8153872e9c6fc98f4023df9c2deaffea2fa463"><code>bd81538</code></a> 2024.07.04 (<a href="https://redirect.github.com/certifi/python-certifi/issues/295">#295</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/06a2cbf21f345563dde6c28b60e29d57e9b210b3"><code>06a2cbf</code></a> Bump peter-evans/create-pull-request from 6.0.5 to 6.1.0 (<a href="https://redirect.github.com/certifi/python-certifi/issues/294">#294</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/13bba02b72bac97c432c277158bc04b4d2a6bc23"><code>13bba02</code></a> Bump actions/checkout from 4.1.6 to 4.1.7 (<a href="https://redirect.github.com/certifi/python-certifi/issues/293">#293</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/e8abcd0e62b334c164b95d49fcabdc9ecbca0554"><code>e8abcd0</code></a> Bump pypa/gh-action-pypi-publish from 1.8.14 to 1.9.0 (<a href="https://redirect.github.com/certifi/python-certifi/issues/292">#292</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/124f4adf171e15cd9a91a8b6e0325ecc97be8fe1"><code>124f4ad</code></a> 2024.06.02 (<a href="https://redirect.github.com/certifi/python-certifi/issues/291">#291</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/c2196ce5d6ee675b27755a19948480a7823e2c6a"><code>c2196ce</code></a> --- (<a href="https://redirect.github.com/certifi/python-certifi/issues/290">#290</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/fefdeec7588ff1c05214b85a552afcad5fdb51b2"><code>fefdeec</code></a> Bump actions/checkout from 4.1.4 to 4.1.5 (<a href="https://redirect.github.com/certifi/python-certifi/issues/289">#289</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/3c5fb1560b826a7f83f1f9750173ff766492c9cf"><code>3c5fb15</code></a> Bump actions/download-artifact from 4.1.6 to 4.1.7 (<a href="https://redirect.github.com/certifi/python-certifi/issues/286">#286</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/4a9569a3eb58db8548536fc16c5c5c7af946a5b1"><code>4a9569a</code></a> Bump actions/checkout from 4.1.2 to 4.1.4 (<a href="https://redirect.github.com/certifi/python-certifi/issues/287">#287</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/1fc808626a895a916b1e4c2b63abae6c5eafdbe3"><code>1fc8086</code></a> Bump peter-evans/create-pull-request from 6.0.4 to 6.0.5 (<a href="https://redirect.github.com/certifi/python-certifi/issues/288">#288</a>)</li> <li>Additional commits viewable in <a href="https://github.com/certifi/python-certifi/compare/2024.02.02...2024.07.04">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=certifi&package-manager=pip&previous-version=2024.2.2&new-version=2024.7.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/intel/llvm/network/alerts). </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

@akx

…es (#14468) Bumps the llvm-docs-requirements group with 6 updates in the /llvm/docs directory: | Package | From | To | | --- | --- | --- | | [babel](https://github.com/python-babel/babel) | `2.14.0` | `2.15.0` | | [furo](https://github.com/pradyunsg/furo) | `2024.4.27` | `2024.5.6` | | [mdit-py-plugins](https://github.com/executablebooks/mdit-py-plugins) | `0.4.0` | `0.4.1` | | [packaging](https://github.com/pypa/packaging) | `24.0` | `24.1` | | [pygments](https://github.com/pygments/pygments) | `2.17.2` | `2.18.0` | | [requests](https://github.com/psf/requests) | `2.32.0` | `2.32.3` | Updates `babel` from 2.14.0 to 2.15.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/python-babel/babel/releases">babel's releases</a>.</em></p> <blockquote> <h2>v2.15.0</h2> <p>The changelog below is auto-generated by GitHub.</p> <p>The binary artifacts attached to this GitHub release <a href="https://github.com/python-babel/babel/actions/runs/8958743141#artifacts">were generated by the GitHub Actions workflow</a>.</p> <p>Please see <a href="https://github.com/python-babel/babel/blob/40b194f4777366e95cc2dfb680fd696b86ef1c04/CHANGES.rst">CHANGELOG.rst</a> for additional details.</p> <hr /> <h2>What's Changed</h2> <ul> <li>Drop support for Python 3.7 (EOL since June 2023) by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1048">python-babel/babel#1048</a></li> <li>Upgrade GitHub Actions by <a href="https://github.com/cclauss"><code>@cclauss</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1054">python-babel/babel#1054</a></li> <li>Improve .po IO by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1068">python-babel/babel#1068</a></li> <li>Use CLDR 44 by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1071">python-babel/babel#1071</a></li> <li>Allow alternative space characters as group separator when parsing numbers by <a href="https://github.com/ronnix"><code>@ronnix</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1007">python-babel/babel#1007</a></li> <li>Include Unicode license in <code>locale-data</code> and in documentation by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1074">python-babel/babel#1074</a></li> <li>Encode support for the "fall back to short format" logic for time delta formatting by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1075">python-babel/babel#1075</a></li> <li>Prepare for 2.15.0 release by <a href="https://github.com/akx"><code>@akx</code></a> in <a href="https://redirect.github.com/python-babel/babel/pull/1079">python-babel/babel#1079</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/cclauss"><code>@cclauss</code></a> made their first contribution in <a href="https://redirect.github.com/python-babel/babel/pull/1054">python-babel/babel#1054</a></li> <li><a href="https://github.com/ronnix"><code>@ronnix</code></a> made their first contribution in <a href="https://redirect.github.com/python-babel/babel/pull/1007">python-babel/babel#1007</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-babel/babel/compare/v2.14.0...v2.15.0">https://github.com/python-babel/babel/compare/v2.14.0...v2.15.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/python-babel/babel/blob/master/CHANGES.rst">babel's changelog</a>.</em></p> <blockquote> <h2>Version 2.15.0</h2> <p>Python version support</p> <pre><code> * Babel 2.15.0 will require Python 3.8 or newer. (:gh:`1048`) <p>Features</p> <pre><code> * CLDR: Upgrade to CLDR 44 (:gh:`1071`) (@akx) * Dates: Support for the &quot;fall back to short format&quot; logic for time delta formatting (:gh:`1075`) (@akx) * Message: More versatile .po IO functions (:gh:`1068`) (@akx) * Numbers: Improved support for alternate spaces when parsing numbers (:gh:`1007`) (@ronnix's first contribution) Infrastructure </code></pre> <ul> <li>Upgrade GitHub Actions (:gh:<code>1054</code>) (<a href="https://github.com/cclauss"><code>@cclauss</code></a>'s first contribution)</li> <li>The Unicode license is now included in <code>locale-data</code> and in the documentation (:gh:<code>1074</code>) (<a href="https://github.com/akx"><code>@akx</code></a>)<br /> </code></pre></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/python-babel/babel/commit/40b194f4777366e95cc2dfb680fd696b86ef1c04"><code>40b194f</code></a> Prepare for 2.15.0 release (<a href="https://redirect.github.com/python-babel/babel/issues/1079">#1079</a>)</li> <li><a href="https://github.com/python-babel/babel/commit/c2e6c6e538418f4c195275c1afff831c4706c2e1"><code>c2e6c6e</code></a> Encode support for the "fall back to short format" logic for time delta forma...</li> <li><a href="https://github.com/python-babel/babel/commit/1a03526e2dda9818424c400530163464a2e74b9b"><code>1a03526</code></a> Include Unicode license in <code>locale-data</code> and in documentation (<a href="https://redirect.github.com/python-babel/babel/issues/1074">#1074</a>)</li> <li><a href="https://github.com/python-babel/babel/commit/c0fb56e6a5a7fa9268b5164db0ff0fc28524d648"><code>c0fb56e</code></a> Allow alternative space characters as group separator when parsing numbers (#...</li> <li><a href="https://github.com/python-babel/babel/commit/fe82fbc90d8044d17bfc4ae1c7a0cb24e85153ef"><code>fe82fbc</code></a> Use CLDR 44 and adjust tests to match new data (<a href="https://redirect.github.com/python-babel/babel/issues/1071">#1071</a>)</li> <li><a href="https://github.com/python-babel/babel/commit/e0d10183635b9ae1d37c31811e23c8974a1bc31e"><code>e0d1018</code></a> Improve .po IO (<a href="https://redirect.github.com/python-babel/babel/issues/1068">#1068</a>)</li> <li><a href="https://github.com/python-babel/babel/commit/40e60a1f6cf178d9f57fcc14f157ea1b2ab77361"><code>40e60a1</code></a> Upgrade GitHub Actions (<a href="https://redirect.github.com/python-babel/babel/issues/1054">#1054</a>)</li> <li><a href="https://github.com/python-babel/babel/commit/2a1709a7768f6f07c3d2dbfdb03d3c8a6bd80aef"><code>2a1709a</code></a> Drop support for Python 3.7 (EOL since June 2023) (<a href="https://redirect.github.com/python-babel/babel/issues/1048">#1048</a>)</li> <li>See full diff in <a href="https://github.com/python-babel/babel/compare/v2.14.0...v2.15.0">compare view</a></li> </ul> </details> <br /> Updates `furo` from 2024.4.27 to 2024.5.6 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pradyunsg/furo/blob/main/docs/changelog.md">furo's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1>  <h2>2024.05.06 -- Cheerful Cerulean</h2> <ul> <li>✨ Add new custom icons for auto mode, reflecting the currently active theme.</li> <li>✨ Add a view this page button.</li> <li>✨ Add colours and highlighting to "version modified" API helpers.</li> <li>✨ Add release information to various customisation knobs.</li> <li>Make all icons bigger and use a thinner stroke with them.</li> </ul> <h2>2024.04.27 -- Bold Burgundy</h2> <ul> <li>Add a skip to content link.</li> <li>Add <code>--font-stack--headings</code>.</li> <li>Add <code>:visited</code> colour and enforce uniform contrast between light/dark.</li> <li>Add an offset of <code>:target</code> to reduce back-to-top overlap.</li> <li>Improve dark mode colours.</li> <li>Fix outstanding colour contrast warnings on Firefox.</li> <li>Fix bad indent in footnotes.</li> <li>Tweak handling of default configuration options in a more resilient manner.</li> <li>Tweak length and sizing of API <code>source</code> links.</li> <li>Stop search engine indexing on search page.</li> </ul> <h2>2024.01.29 -- Amazing Amethyst</h2> <ul> <li>Fix canonical url when building with <code>dirhtml</code>.</li> <li>Relicense the demo module.</li> </ul> <h2>2023.09.10 -- Zesty Zaffre</h2> <ul> <li>Make asset hash injection idempotent, fixing Sphinx 6 compatibility.</li> <li>Fix the check for HTML builders, fixing non-HTML Read the Docs builds.</li> </ul> <h2>2023.08.19 -- Xenolithic Xanadu</h2> <ul> <li>Fix missing search context with Sphinx 7.2, for dirhtml builds.</li> <li>Drop support for Python 3.7.</li> <li>Present configuration errors in a better format -- thanks <a href="https://github.com/AA-Turner"><code>@AA-Turner</code></a>!</li> <li>Bump <code>require_sphinx()</code> to Sphinx 6.0, in line with dependency changes in Unassuming Ultramarine.</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pradyunsg/furo/commit/b087e931bec009e4dffc98dab0ed85b2511d4bb6"><code>b087e93</code></a> Prepare release: 2024.05.06</li> <li><a href="https://github.com/pradyunsg/furo/commit/169c63dcc6f79314f5f54d8ce960ef14e51eaf11"><code>169c63d</code></a> Update the changelog</li> <li><a href="https://github.com/pradyunsg/furo/commit/b7ec84d9c1e259d21de8fde980d9df7f1687f2a5"><code>b7ec84d</code></a> Drop discussion of Sphinx's <code>basic</code> theme</li> <li><a href="https://github.com/pradyunsg/furo/commit/2cd4d4a883b472c81c7ccf908a8bae0b2b8e1792"><code>2cd4d4a</code></a> Demote the note about inherited from <code>basic</code> configuration</li> <li><a href="https://github.com/pradyunsg/furo/commit/983d6c396aa1a151a05db17c756aa3c2fb5ea4ef"><code>983d6c3</code></a> Tweak the colours for API <code>versionmodified</code> information</li> <li><a href="https://github.com/pradyunsg/furo/commit/1ffbf767cc9378c795224f45fe7136a738e11afc"><code>1ffbf76</code></a> Add release information to various customisation knobs</li> <li><a href="https://github.com/pradyunsg/furo/commit/2c386b9da563884ee9d293d74bab2886c8f28320"><code>2c386b9</code></a> Use the appropriate Sphinx directive instead of weird text</li> <li><a href="https://github.com/pradyunsg/furo/commit/ec8815ae68b287bf2d2ae923238963a50d2812f6"><code>ec8815a</code></a> Add (back?) support for RtD context inference on top of page buttons</li> <li><a href="https://github.com/pradyunsg/furo/commit/1b4cf89684ae5a7819082f2918729045f76589f6"><code>1b4cf89</code></a> Bump the npm group with 5 updates (<a href="https://redirect.github.com/pradyunsg/furo/issues/793">#793</a>)</li> <li><a href="https://github.com/pradyunsg/furo/commit/ce8fb1079b1112f788bccd292538b1cdce37c5ab"><code>ce8fb10</code></a> Bump the github-actions group with 3 updates (<a href="https://redirect.github.com/pradyunsg/furo/issues/792">#792</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pradyunsg/furo/compare/2024.04.27...2024.05.06">compare view</a></li> </ul> </details> <br /> Updates `mdit-py-plugins` from 0.4.0 to 0.4.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/executablebooks/mdit-py-plugins/releases">mdit-py-plugins's releases</a>.</em></p> <blockquote> <h2>v0.4.1</h2> <h2>What's Changed</h2> <ul> <li> <p>👌 Expand support for Python-Markdown in the admon plugin by <a href="https://github.com/KyleKing"><code>@KyleKing</code></a> in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/94">executablebooks/mdit-py-plugins#94</a></p> </li> <li> <p>👌 Add option for footnotes references to always be matched by <a href="https://github.com/chrisjsewell"><code>@chrisjsewell</code></a> in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/108">executablebooks/mdit-py-plugins#108</a></p> </li> <li> <p>🔧 Export plugins explicitly with <code>__all__</code> by <a href="https://github.com/llimllib"><code>@llimllib</code></a> in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/91">executablebooks/mdit-py-plugins#91</a></p> </li> <li> <p>🔧 Use ruff-format by <a href="https://github.com/chrisjsewell"><code>@chrisjsewell</code></a> in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/107">executablebooks/mdit-py-plugins#107</a></p> </li> <li> <p>🧪 Test against 3.12 by <a href="https://github.com/chrisjsewell"><code>@chrisjsewell</code></a> in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/109">executablebooks/mdit-py-plugins#109</a></p> </li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/llimllib"><code>@llimllib</code></a> made their first contribution in <a href="https://redirect.github.com/executablebooks/mdit-py-plugins/pull/91">executablebooks/mdit-py-plugins#91</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/executablebooks/mdit-py-plugins/compare/v0.4.0...v0.4.1">https://github.com/executablebooks/mdit-py-plugins/compare/v0.4.0...v0.4.1</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/executablebooks/mdit-py-plugins/blob/master/CHANGELOG.md">mdit-py-plugins's changelog</a>.</em></p> <blockquote> <h2>0.4.1 - 2024-05-12</h2> <ul> <li> <p>👌 Add option for footnotes references to always be matched</p> <p>Usually footnote references are only matched when a footnote definition of the same label has already been found. If <code>always_match_refs=True</code>, any <code>[^...]</code> syntax will be treated as a footnote.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/d11bdaf0979e6fae01c35db5a4d1f6a4b4dd8843"><code>d11bdaf</code></a> 🚀 Release v0.4.1 (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/110">#110</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/aa1f557ea65a79447f828fadb19d89b94fbe1976"><code>aa1f557</code></a> 🧪 Test against 3.12 (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/109">#109</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/33c27e0f18024f26847cae6b1f77ccd572643864"><code>33c27e0</code></a> 👌 Add option for footnotes references to always be matched (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/108">#108</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/77624583c2ca7d58e08d1e602364476e25742a9b"><code>7762458</code></a> 🔧 Use ruff-format (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/107">#107</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/950908b2ef69924633c4f085800d7cede996d124"><code>950908b</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/100">#100</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/14dfd1ade0b3f60c0b066a0467fd5b752fa5f2bb"><code>14dfd1a</code></a> ⬆️ Bump actions/setup-python from 4 to 5 (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/101">#101</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/bd8d37d52d370271900dda3861129984f899f596"><code>bd8d37d</code></a> ⬆️ Bump actions/checkout from 3 to 4 (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/98">#98</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/867a77a0f22ce1732ebf023e3fb623febabd41f6"><code>867a77a</code></a> 👌 Expand support for Python-Markdown in the admon plugin (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/94">#94</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/3829c8453caead90f9df97a1491556de97bfd644"><code>3829c84</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/90">#90</a>)</li> <li><a href="https://github.com/executablebooks/mdit-py-plugins/commit/ba0c31e762d4961b6fde1b27541be92084af877b"><code>ba0c31e</code></a> 🔧 Export plugins explicitly with <code>__all__</code> (<a href="https://redirect.github.com/executablebooks/mdit-py-plugins/issues/91">#91</a>)</li> <li>See full diff in <a href="https://github.com/executablebooks/mdit-py-plugins/compare/v0.4.0...v0.4.1">compare view</a></li> </ul> </details> <br /> Updates `packaging` from 24.0 to 24.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pypa/packaging/releases">packaging's releases</a>.</em></p> <blockquote> <h2>24.1</h2> <h2>What's Changed</h2> <ul> <li>pyupgrade/black/isort/flake8 → ruff by <a href="https://github.com/DimitriPapadopoulos"><code>@DimitriPapadopoulos</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/769">pypa/packaging#769</a></li> <li>Add support for Python 3.13 and drop EOL 3.7 by <a href="https://github.com/hugovk"><code>@hugovk</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/783">pypa/packaging#783</a></li> <li>Bump the github-actions group with 4 updates by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/782">pypa/packaging#782</a></li> <li>Fix typo in <code>_parser</code> docstring by <a href="https://github.com/pradyunsg"><code>@pradyunsg</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/784">pypa/packaging#784</a></li> <li>Modernise type annotations using FA rules from ruff by <a href="https://github.com/pradyunsg"><code>@pradyunsg</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/785">pypa/packaging#785</a></li> <li>Document <code>markers.default_environment()</code> by <a href="https://github.com/edgarrmondragon"><code>@edgarrmondragon</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/753">pypa/packaging#753</a></li> <li>Bump the github-actions group with 3 updates by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/789">pypa/packaging#789</a></li> <li>Work around platform.python_version() returning non PEP 440 compliant version for non-tagged CPython builds by <a href="https://github.com/sbidoul"><code>@sbidoul</code></a> in <a href="https://redirect.github.com/pypa/packaging/pull/802">pypa/packaging#802</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/dependabot"><code>@dependabot</code></a> made their first contribution in <a href="https://redirect.github.com/pypa/packaging/pull/782">pypa/packaging#782</a></li> <li><a href="https://github.com/edgarrmondragon"><code>@edgarrmondragon</code></a> made their first contribution in <a href="https://redirect.github.com/pypa/packaging/pull/753">pypa/packaging#753</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pypa/packaging/compare/24.0...24.1">https://github.com/pypa/packaging/compare/24.0...24.1</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/packaging/blob/main/CHANGELOG.rst">packaging's changelog</a>.</em></p> <blockquote> <p>24.1 - 2024-06-10</p> <pre><code> No unreleased changes. </code></pre> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/packaging/commit/85442b8032cb7bae72866dfd7782234a98dd2fb7"><code>85442b8</code></a> Bump for release</li> <li><a href="https://github.com/pypa/packaging/commit/3e67fc775e93166600c84a5183ab6a86afff84b5"><code>3e67fc7</code></a> Work around <code>platform.python_version()</code> returning non PEP 440 compliant versi...</li> <li><a href="https://github.com/pypa/packaging/commit/32deafe8668a2130a3366b98154914d188f3718e"><code>32deafe</code></a> Bump the github-actions group with 3 updates (<a href="https://redirect.github.com/pypa/packaging/issues/789">#789</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/e0dda88874e73cd484b9e8464c5921a903db3cf0"><code>e0dda88</code></a> Document <code>markers.default_environment()</code> (<a href="https://redirect.github.com/pypa/packaging/issues/753">#753</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/cc938f984bbbe43c5734b9656c9837ab3a28191f"><code>cc938f9</code></a> Modernise type annotations using FA rules from ruff (<a href="https://redirect.github.com/pypa/packaging/issues/785">#785</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/757f559404ff6cc1cdef59a2c3628ccdaa505ac4"><code>757f559</code></a> Fix typo in <code>_parser</code> docstring (<a href="https://redirect.github.com/pypa/packaging/issues/784">#784</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/ec9f203a9f1d336d62b71a26e3ad3dfcfbef92dc"><code>ec9f203</code></a> Bump the github-actions group with 4 updates (<a href="https://redirect.github.com/pypa/packaging/issues/782">#782</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/5cbe1e44cc7b0497a11ab441310a86a5ebf1658a"><code>5cbe1e4</code></a> Add support for Python 3.13 and drop EOL 3.7 (<a href="https://redirect.github.com/pypa/packaging/issues/783">#783</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/cb8fd38ef4c4189142702951b89dee1f09e4d71f"><code>cb8fd38</code></a> pyupgrade/black/isort/flake8 → ruff (<a href="https://redirect.github.com/pypa/packaging/issues/769">#769</a>)</li> <li><a href="https://github.com/pypa/packaging/commit/e8002b16e79c71a5f256d4f20eee0170f4327dd9"><code>e8002b1</code></a> Bump for development</li> <li>See full diff in <a href="https://github.com/pypa/packaging/compare/24.0...24.1">compare view</a></li> </ul> </details> <br /> Updates `pygments` from 2.17.2 to 2.18.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pygments/pygments/releases">pygments's releases</a>.</em></p> <blockquote> <h2>2.18.0</h2> <ul> <li> <p>New lexers:</p> <ul> <li>Janet (<a href="https://redirect.github.com/pygments/pygments/issues/2557">#2557</a>)</li> <li>Lean 4 (<a href="https://redirect.github.com/pygments/pygments/issues/2618">#2618</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2626">#2626</a>)</li> <li>Luau (<a href="https://redirect.github.com/pygments/pygments/issues/2605">#2605</a>)</li> <li>Mojo (<a href="https://redirect.github.com/pygments/pygments/issues/2691">#2691</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2515">#2515</a>)</li> <li>org-mode (<a href="https://redirect.github.com/pygments/pygments/issues/2628">#2628</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2636">#2636</a>)</li> <li>Promela (<a href="https://redirect.github.com/pygments/pygments/issues/2620">#2620</a>)</li> <li>Soong / <code>Android.bp</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2659">#2659</a>)</li> <li>Tact (<a href="https://redirect.github.com/pygments/pygments/issues/2571">#2571</a>)</li> <li>Typst (<a href="https://redirect.github.com/pygments/pygments/issues/2596">#2596</a>)</li> </ul> </li> <li> <p>Updated lexers:</p> <ul> <li>Awk: recognize ternary operator (<a href="https://redirect.github.com/pygments/pygments/issues/2687">#2687</a>)</li> <li>Bash: add <code>openrc</code> alias (<a href="https://redirect.github.com/pygments/pygments/issues/2599">#2599</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2371">#2371</a>)</li> <li>Coq: add keywords, lex more vernacular command arguments, produce fewer tokens on heading comments (<a href="https://redirect.github.com/pygments/pygments/issues/2678">#2678</a>)</li> <li>DNS zone files: Fix comment parsing (<a href="https://redirect.github.com/pygments/pygments/issues/2595">#2595</a>)</li> <li>Hy: Support unicode literals (<a href="https://redirect.github.com/pygments/pygments/issues/1126">#1126</a>)</li> <li>Inform6: Update to Inform 6.42 (<a href="https://redirect.github.com/pygments/pygments/issues/2644">#2644</a>)</li> <li>lean: Fix name handling (<a href="https://redirect.github.com/pygments/pygments/issues/2614">#2614</a>)</li> <li>Logtalk: add <code>uninstantiation</code> keyword and recognize escape sequences (<a href="https://redirect.github.com/pygments/pygments/issues/2619">#2619</a>)</li> <li>Macaulay2: Update to 1.23 (<a href="https://redirect.github.com/pygments/pygments/issues/2655">#2655</a>)</li> <li>Python: fix highlighting of soft keywords before <code>None</code>/<code>True</code>/<code>False</code></li> <li>reStructuredText: use <code>Token.Comment</code> for comments instead of <code>Comment.Preproc</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2598">#2598</a>)</li> <li>Rust: highlight <code>:</code>, <code>::</code> and <code>-></code> as <code>Punctuation</code> and whitespace as <code>Whitespace</code>, instead of <code>Text</code> in both cases (<a href="https://redirect.github.com/pygments/pygments/issues/2631">#2631</a>)</li> <li>Spice: Add keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2621">#2621</a>)</li> <li>SQL Explain: allow negative numbers (<a href="https://redirect.github.com/pygments/pygments/issues/2610">#2610</a>)</li> <li>Swift: Support multiline strings (<a href="https://redirect.github.com/pygments/pygments/issues/2681">#2681</a>)</li> <li>ThingsDB: add constants and new functions; support template strings (<a href="https://redirect.github.com/pygments/pygments/issues/2624">#2624</a>)</li> <li>UL4: support nested <code><?doc?></code> and <code><?note?></code> tags (<a href="https://redirect.github.com/pygments/pygments/issues/2597">#2597</a>)</li> <li>VHDL: support multi-line comments of VHDL-2008 (<a href="https://redirect.github.com/pygments/pygments/issues/2622">#2622</a>)</li> <li>Wikitext: Remove <code>kk-*</code> in <code>variant_langs</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2647">#2647</a>)</li> <li>Xtend: Add <code>val</code> and <code>var</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2602">#2602</a>)</li> </ul> </li> <li> <p>New styles:</p> <ul> <li>Coffee (<a href="https://redirect.github.com/pygments/pygments/issues/2609">#2609</a>)</li> </ul> </li> <li> <p>Make background colors in the image formatter work with Pillow 10.0 (<a href="https://redirect.github.com/pygments/pygments/issues/2623">#2623</a>)</p> </li> <li> <p>Require Python 3.8. As a result, the <code>importlib-metadata</code> package is no longer needed for fast plugin discovery on Python 3.7. The <code>plugins</code> extra (used as, e.g., <code>pip install pygments[plugins]</code>)</p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pygments/pygments/blob/master/CHANGES">pygments's changelog</a>.</em></p> <blockquote> <h2>Version 2.18.0</h2> <p>(released May 4th, 2024)</p> <ul> <li> <p>New lexers:</p> <ul> <li>Janet (<a href="https://redirect.github.com/pygments/pygments/issues/2557">#2557</a>)</li> <li>Lean 4 (<a href="https://redirect.github.com/pygments/pygments/issues/2618">#2618</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2626">#2626</a>)</li> <li>Luau (<a href="https://redirect.github.com/pygments/pygments/issues/2605">#2605</a>)</li> <li>Mojo (<a href="https://redirect.github.com/pygments/pygments/issues/2691">#2691</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2515">#2515</a>)</li> <li>org-mode (<a href="https://redirect.github.com/pygments/pygments/issues/2628">#2628</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2636">#2636</a>)</li> <li>Promela (<a href="https://redirect.github.com/pygments/pygments/issues/2620">#2620</a>)</li> <li>Soong / <code>Android.bp</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2659">#2659</a>)</li> <li>Tact (<a href="https://redirect.github.com/pygments/pygments/issues/2571">#2571</a>)</li> <li>Typst (<a href="https://redirect.github.com/pygments/pygments/issues/2596">#2596</a>)</li> </ul> </li> <li> <p>Updated lexers:</p> <ul> <li>Awk: recognize ternary operator (<a href="https://redirect.github.com/pygments/pygments/issues/2687">#2687</a>)</li> <li>Bash: add <code>openrc</code> alias (<a href="https://redirect.github.com/pygments/pygments/issues/2599">#2599</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2371">#2371</a>)</li> <li>Coq: add keywords, lex more vernacular command arguments, produce fewer tokens on heading comments (<a href="https://redirect.github.com/pygments/pygments/issues/2678">#2678</a>)</li> <li>DNS zone files: Fix comment parsing (<a href="https://redirect.github.com/pygments/pygments/issues/2595">#2595</a>)</li> <li>Hy: Support unicode literals (<a href="https://redirect.github.com/pygments/pygments/issues/1126">#1126</a>)</li> <li>Inform6: Update to Inform 6.42 (<a href="https://redirect.github.com/pygments/pygments/issues/2644">#2644</a>)</li> <li>lean: Fix name handling (<a href="https://redirect.github.com/pygments/pygments/issues/2614">#2614</a>)</li> <li>Logtalk: add <code>uninstantiation</code> keyword and recognize escape sequences (<a href="https://redirect.github.com/pygments/pygments/issues/2619">#2619</a>)</li> <li>Macaulay2: Update to 1.23 (<a href="https://redirect.github.com/pygments/pygments/issues/2655">#2655</a>)</li> <li>Python: fix highlighting of soft keywords before <code>None</code>/<code>True</code>/<code>False</code></li> <li>reStructuredText: use <code>Token.Comment</code> for comments instead of <code>Comment.Preproc</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2598">#2598</a>)</li> <li>Rust: highlight <code>:</code>, <code>::</code> and <code>-></code> as <code>Punctuation</code> and whitespace as <code>Whitespace</code>, instead of <code>Text</code> in both cases (<a href="https://redirect.github.com/pygments/pygments/issues/2631">#2631</a>)</li> <li>Spice: Add keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2621">#2621</a>)</li> <li>SQL Explain: allow negative numbers (<a href="https://redirect.github.com/pygments/pygments/issues/2610">#2610</a>)</li> <li>Swift: Support multiline strings (<a href="https://redirect.github.com/pygments/pygments/issues/2681">#2681</a>)</li> <li>ThingsDB: add constants and new functions; support template strings (<a href="https://redirect.github.com/pygments/pygments/issues/2624">#2624</a>)</li> <li>UL4: support nested <code><?doc?></code> and <code><?note?></code> tags (<a href="https://redirect.github.com/pygments/pygments/issues/2597">#2597</a>)</li> <li>VHDL: support multi-line comments of VHDL-2008 (<a href="https://redirect.github.com/pygments/pygments/issues/2622">#2622</a>)</li> <li>Wikitext: Remove <code>kk-*</code> in <code>variant_langs</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2647">#2647</a>)</li> <li>Xtend: Add <code>val</code> and <code>var</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2602">#2602</a>)</li> </ul> </li> <li> <p>New styles:</p> <ul> <li>Coffee (<a href="https://redirect.github.com/pygments/pygments/issues/2609">#2609</a>)</li> </ul> </li> <li> <p>Make background colors in the image formatter work with Pillow 10.0 (<a href="https://redirect.github.com/pygments/pygments/issues/2623">#2623</a>)</p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pygments/pygments/commit/d7d11f6e6d3aa97805215c1cc833ea5f0ef1fcbb"><code>d7d11f6</code></a> Last steps for 2.18 release.</li> <li><a href="https://github.com/pygments/pygments/commit/ec7bfd2cc91a1bb2a7200b27c2c553309d689839"><code>ec7bfd2</code></a> Fix Janet version_added.</li> <li><a href="https://github.com/pygments/pygments/commit/ea9c8232b4edfdc7193f25f1253040e77342f878"><code>ea9c823</code></a> Update CHANGES.</li> <li><a href="https://github.com/pygments/pygments/commit/338d36665371cd9e4193b59a267d4f576d8eb05d"><code>338d366</code></a> Merge pull request <a href="https://redirect.github.com/pygments/pygments/issues/2670">#2670</a> from Kodiologist/hylex</li> <li><a href="https://github.com/pygments/pygments/commit/4d1371b30af2de7c6a74af6ef64673b657dfe3ea"><code>4d1371b</code></a> Lock down the pytest version.</li> <li><a href="https://github.com/pygments/pygments/commit/8dd97e04d47437581ca2fcb19a94aeb5cbd1dba2"><code>8dd97e0</code></a> Improve docs.</li> <li><a href="https://github.com/pygments/pygments/commit/26179d66122f2afacdc115071ce344af1984a55c"><code>26179d6</code></a> Fix deprecated variable usage in tests.</li> <li><a href="https://github.com/pygments/pygments/commit/ad125ca614097b5b02c4603bdbe63ec79b791473"><code>ad125ca</code></a> Prepare 2.18 release.</li> <li><a href="https://github.com/pygments/pygments/commit/24deeb9cae597db4d22496b0c2cc9e82d3e8a689"><code>24deeb9</code></a> Lock the ruff version in tox.ini.</li> <li><a href="https://github.com/pygments/pygments/commit/c9165cf7fb18f01066222ec7d063e5e5975f2a69"><code>c9165cf</code></a> Fix format string usage.</li> <li>Additional commits viewable in <a href="https://github.com/pygments/pygments/compare/2.17.2...2.18.0">compare view</a></li> </ul> </details> <br /> Updates `requests` from 2.32.0 to 2.32.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/psf/requests/releases">requests's releases</a>.</em></p> <blockquote> <h2>v2.32.3</h2> <h2>2.32.3 (2024-05-29)</h2> <p><strong>Bugfixes</strong></p> <ul> <li>Fixed bug breaking the ability to specify custom SSLContexts in sub-classes of HTTPAdapter. (<a href="https://redirect.github.com/psf/requests/issues/6716">#6716</a>)</li> <li>Fixed issue where Requests started failing to run on Python versions compiled without the <code>ssl</code> module. (<a href="https://redirect.github.com/psf/requests/issues/6724">#6724</a>)</li> </ul> <h2>v2.32.2</h2> <h2>2.32.2 (2024-05-21)</h2> <p><strong>Deprecations</strong></p> <ul> <li> <p>To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0, we've renamed <code>_get_connection</code> to a new public API, <code>get_connection_with_tls_context</code>. Existing custom HTTPAdapters will need to migrate their code to use this new API. <code>get_connection</code> is considered deprecated in all versions of Requests>=2.32.0.</p> <p>A minimal (2-line) example has been provided in the linked PR to ease migration, but we strongly urge users to evaluate if their custom adapter is subject to the same issue described in CVE-2024-35195. (<a href="https://redirect.github.com/psf/requests/issues/6710">#6710</a>)</p> </li> </ul> <h2>v2.32.1</h2> <h2>2.32.1 (2024-05-20)</h2> <p><strong>Bugfixes</strong></p> <ul> <li>Add missing test certs to the sdist distributed on PyPI.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/psf/requests/blob/main/HISTORY.md">requests's changelog</a>.</em></p> <blockquote> <h2>2.32.3 (2024-05-29)</h2> <p><strong>Bugfixes</strong></p> <ul> <li>Fixed bug breaking the ability to specify custom SSLContexts in sub-classes of HTTPAdapter. (<a href="https://redirect.github.com/psf/requests/issues/6716">#6716</a>)</li> <li>Fixed issue where Requests started failing to run on Python versions compiled without the <code>ssl</code> module. (<a href="https://redirect.github.com/psf/requests/issues/6724">#6724</a>)</li> </ul> <h2>2.32.2 (2024-05-21)</h2> <p><strong>Deprecations</strong></p> <ul> <li> <p>To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0, we've renamed <code>_get_connection</code> to a new public API, <code>get_connection_with_tls_context</code>. Existing custom HTTPAdapters will need to migrate their code to use this new API. <code>get_connection</code> is considered deprecated in all versions of Requests>=2.32.0.</p> <p>A minimal (2-line) example has been provided in the linked PR to ease migration, but we strongly urge users to evaluate if their custom adapter is subject to the same issue described in CVE-2024-35195. (<a href="https://redirect.github.com/psf/requests/issues/6710">#6710</a>)</p> </li> </ul> <h2>2.32.1 (2024-05-20)</h2> <p><strong>Bugfixes</strong></p> <ul> <li>Add missing test certs to the sdist distributed on PyPI.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/psf/requests/commit/0e322af87745eff34caffe4df68456ebc20d9068"><code>0e322af</code></a> v2.32.3</li> <li><a href="https://github.com/psf/requests/commit/e18879932287c2bf4bcee4ddf6ccb8a69b6fc656"><code>e188799</code></a> Don't create default SSLContext if ssl module isn't present (<a href="https://redirect.github.com/psf/requests/issues/6724">#6724</a>)</li> <li><a href="https://github.com/psf/requests/commit/145b5399486b56e00250204f033441f3fdf2f3c9"><code>145b539</code></a> Merge pull request <a href="https://redirect.github.com/psf/requests/issues/6716">#6716</a> from sigmavirus24/bug/6715</li> <li><a href="https://github.com/psf/requests/commit/b1d73ddb509a3a2d3e10744e85f9cdebdbde90f0"><code>b1d73dd</code></a> Don't use default SSLContext with custom poolmanager kwargs</li> <li><a href="https://github.com/psf/requests/commit/6badbac6e0d6b5a53872f26401761ad37a9002b8"><code>6badbac</code></a> Update HISTORY.md</li> <li><a href="https://github.com/psf/requests/commit/a62a2d35d918baa8e793f7aa4fb41527644dfca5"><code>a62a2d3</code></a> Allow for overriding of specific pool key params</li> <li><a href="https://github.com/psf/requests/commit/88dce9d854797c05d0ff296b70e0430535ef8aaf"><code>88dce9d</code></a> v2.32.2</li> <li><a href="https://github.com/psf/requests/commit/c98e4d133ef29c46a9b68cd783087218a8075e05"><code>c98e4d1</code></a> Merge pull request <a href="https://redirect.github.com/psf/requests/issues/6710">#6710</a> from nateprewitt/api_rename</li> <li><a href="https://github.com/psf/requests/commit/92075b330a30b9883f466a43d3f7566ab849f91b"><code>92075b3</code></a> Add deprecation warning</li> <li><a href="https://github.com/psf/requests/commit/aa1461b68aa73e2f6ec0e78c8853b635c76fd099"><code>aa1461b</code></a> Move _get_connection to get_connection_with_tls_context</li> <li>Additional commits viewable in <a href="https://github.com/psf/requests/compare/v2.32.0...v2.32.3">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…ster_group (#14113) This PR is a partial implementation of [`sycl_ext_oneapi_cuda_cluster_group`](intel/llvm#13594), introducing the `cluster_size` property to launch a kernel with CUDA's thread block clusters Only a small part of the extension specification described in intel/llvm#13594 is used in this implementation. To be specific everything after the section "Launching a kernel with a `cluster_group`" is not included in this PR. A very important point to note is that this PR still fully represents a functional use case of using Nvidia's cuda driver cluster launch feature for its primary purpose which is to accelerate cross-work-group collective operations (particularly for GEMM), leveraging cross-work group asynchronous multi-casting of distributed shared memory across work-groups. This is a high priority feature that is targeted for the next release. The other parts of the extension specification described in intel/llvm#13594, primarily related to the "cluster_group" abstraction is a (user-facing) convenience abstraction that is not required to be exposed in libraries that optimize such library collective operations (GEMM). Please therefore focus reviews of this PR on the relevant aspects of the extension that are required for the implementation in this PR and the library based application of it as described in this message. --------- Signed-off-by: JackAKirk <[email protected]>

…roup.hpp` (#13760) Not needed anymore after deprecated shuffles/collectives were removed.

Co-authored-by: Kenneth Benzie (Benie) <[email protected]>

We cannot currently update the kernel binary of a node in Whole Graph Update. Rather than silently accepting inconsistent kernel functions, which indicates the graphs aren't topologically identical, throw an error when the kernel types of two nodes are mismatched. This change requires removing the unittest for barrier nodes in Whole Graph Update as the mock infrastructure does not setup the internal `CG` class to the depth required to test working functionality. This functionality is already covered by `test-e2e/Graph/Update/whole_update_barrier_node.cpp`

…n (#14407) pre-commit PR for oneapi-src/unified-runtime#1809 --------- Signed-off-by: Neil R. Spruit <[email protected]> Co-authored-by: Kenneth Benzie (Benie) <[email protected]>

Signed-off-by: Ahmed, Daiyaan <[email protected]>

Commits on Jul 11, 2024

Trigger Build

daiyaan-ahmed6 committed Jul 11, 2024

Configuration menu

View commit details

Copy full SHA for 7d3b3e2

Browse repository at this point

Copy the full SHA

7d3b3e2 View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[SYCLomatic] Fix sycl to SYCLomatic pull down failed. #2143

[SYCLomatic] Fix sycl to SYCLomatic pull down failed. #2143

Commits on Jun 25, 2024

Commits on Jun 26, 2024

Commits on Jun 27, 2024

Commits on Jun 28, 2024

Commits on Jul 1, 2024

Commits on Jul 2, 2024

Commits on Jul 3, 2024

Commits on Jul 4, 2024

Commits on Jul 5, 2024

Commits on Jul 7, 2024

Commits on Jul 8, 2024

Commits on Jul 9, 2024

Commits on Jul 11, 2024

[SYCLomatic] Fix sycl to SYCLomatic pull down failed. #2143

Are you sure you want to change the base?

[SYCLomatic] Fix sycl to SYCLomatic pull down failed. #2143

Commits on Jun 25, 2024

Commits on Jun 26, 2024

Commits on Jun 27, 2024

Commits on Jun 28, 2024

Commits on Jul 1, 2024

Commits on Jul 2, 2024

Commits on Jul 3, 2024

Commits on Jul 4, 2024

Commits on Jul 5, 2024

Commits on Jul 7, 2024

Commits on Jul 8, 2024

Commits on Jul 9, 2024

Commits on Jul 11, 2024