[all-commits] [llvm/llvm-project] eb7d53: [LLVM] Add a C API for creating instructions with ...

[Tim Besard via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: eb7d535199d7fc3de763276093b97141a041d3d6
      https://github.com/llvm/llvm-project/commit/eb7d535199d7fc3de763276093b97141a041d3d6
  Author: Tim Besard <tim.besard at gmail.com>
  Date:   2024-08-20 (Tue, 20 Aug 2024)

  Changed paths:
    M llvm/docs/ReleaseNotes.rst
    M llvm/include/llvm-c/Core.h
    M llvm/include/llvm/IR/Instructions.h
    M llvm/lib/IR/Core.cpp
    M llvm/test/Bindings/llvm-c/echo.ll
    M llvm/tools/llvm-c-test/attributes.c
    M llvm/tools/llvm-c-test/echo.cpp
    M llvm/tools/llvm-c-test/llvm-c-test.h
    M llvm/tools/llvm-c-test/module.c
    M llvm/unittests/IR/InstructionsTest.cpp

  Log Message:
  -----------
  [LLVM] Add a C API for creating instructions with custom syncscopes. (#104775)

Another upstreaming of C API extensions we have in Julia/LLVM.jl.
Although [we went](https://github.com/maleadt/LLVM.jl/pull/431) with a
string-based API there, here I'm proposing something that's similar to
existing metadata/attribute APIs:
- explicit functions to map syncscope names to IDs, and back
- `LLVM*SyncScope` versions of builder APIs that already take a
`SingleThread` argument: atomic rmw, atomic xchg, fence
- `LLVMGetAtomicSyncScopeID` and `LLVMSetAtomicSyncScopeID` for other
atomic instructions
- testing through `llvm-c-test`'s `--echo` functionality



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications