Issue 176439
Summary Request Commit Access for kumarak
Labels infra:commit-access-request
Assignees
Reporter kumarak
    Why Are you requesting commit access ?

Hi there, my name is Akshay Kumar and I am a Compiler Engineer at Trail of Bits

Our team worked on adding constant-time support access to LLVM target backends. We also published our approach in this [RFC](https://discourse.llvm.org/t/rfc-constant-time-coding-support/87781). 

Currently we have ongoing PR's to add this support and is opened by my colleague @wizardengineer. 

[ConstantTime][LLVM] Add llvm.ct.select intrinsic with generic SelectionDAG lowering(https://github.com/llvm/llvm-project/pull/166702)
[ConstantTime][Clang] Add __builtin_ct_select for constant-time selection (https://github.com/llvm/llvm-project/pull/166703)
[ConstantTime] Native ct.select support for X86 and i386 (https://github.com/llvm/llvm-project/pull/166704)
[ConstantTime][MIPS] Add comprehensive tests for ct.select (https://github.com/llvm/llvm-project/pull/166705)
[ConstantTime] Native ct.select support for ARM64 (https://github.com/llvm/llvm-project/pull/166706)
[ConstantTime] Native ct.select support for ARM32 and Thumb (https://github.com/llvm/llvm-project/pull/166707)
[ConstantTime][RISCV] Add comprehensive tests for ct.select (https://github.com/llvm/llvm-project/pull/166708)
[ConstantTime][WebAssembly] Add comprehensive tests for ct.select (https://github.com/llvm/llvm-project/pull/166709)

I’d like to request commit access on these PR branches so I can help address reviewer feedback and push the required updates directly. I understand LLVM’s policy around commit access for contributors without prior merges, and I’m happy for this access to be limited strictly to the above PRs.

If commit access isn’t possible, what’s the best way to proceed? Should we close these and re-open them from a fork so I can push updates. Please suggests. 
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to