일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
- custom packer
- anti debugging
- OSR
- v8 tracing
- Android
- LLVM
- initial-exec
- android inject
- pthread
- tracing
- so inject
- tracerpid
- Linux packer
- Injection
- on stack replacement
- LLVM Obfuscator
- Obfuscator
- linux debugging
- uftrace
- LLVM 난독화
- thread local storage
- on-stack replacement
- v8 optimizing
- pinpoint
- 안티디버깅
- linux thread
- apm
- TLS
- Linux custom packer
- 난독화
- Today
- Total
목록전체 글 (132)
Why should I know this?
* 다른 이슈 스터디 차원에서 먼저 일부 GVN 로직을 다룹니다. ;*** IR Dump After MergedLoadStoreMotionPass on test1 *** ; Function Attrs: mustprogress nofree norecurse nosync nounwind readnone uwtable willreturn define dso_local zeroext i1 @test1(i1 noundef zeroext %a, i1 noundef zeroext %b) local_unnamed_addr #0 { entry: %or5 = or i1 %a, %b br i1 %or5, label %cond.true, label %cond.false cond.true: ; preds = %entry %xo..
이번에 살펴볼 이슈는 이겁니다. https://github.com/llvm/llvm-project/issues/71792 Simplification Comparison for `(a | b) ? (a ^ b) : (a & b)` etc. (Clang13 vs Clang trunk) · Issue #71792 · llvm/llvm-project Consider the following six functions. https://godbolt.org/z/cTsd43jhh bool test1(bool a, bool b) { return (a | b) ? (a ^ b) : (a & b); } bool test2(bool a, bool b) { return (a | b) ? (a & b) : (a ^... gith..
패치 링크 : https://github.com/llvm/llvm-project/issues/70578 [MemCpyOpt] The store instruction should not be removed by DSE. · Issue #70578 · llvm/llvm-project This IR is reduced from rust-lang/rust#116976. declare void @f_byval(ptr byval(i32)) declare void @llvm.memcpy.p0.p0.i64(ptr, ptr, i64, i1) define void @byval_param_noalias_metadata(ptr align 4 byv... github.com 문제 IR https://llvm.godbolt.or..
https://discourse.llvm.org/t/how-does-byval-work/62397/3 How does byval work? Yeah I’m actually looking for the behavior as it is now. I’m not implementing a new backend, I’m trying to see if byval passes it on the stack on all platforms (arm, aarch64, x86_64, i386, etc), so I was wondering if there is a default behavior here discourse.llvm.org
(gdb) bt #0 0x00005555562eebc6 in llvm::BatchAAResults::getModRefInfo (this=0x7fffffffb980, I=0x55555ceb46a0, OptLoc=std::optional [no contained value]) at /home/m/llvm-project/llvm/include/llvm/Analysis/AliasAnalysis.h:641 #1 0x000055555657a3de in llvm::MemorySSA::createNewAccess (this=0x55555ce56230, I=0x55555ceb46a0, AAP=0x7fffffffb980, Template=0x0) at /home/m/llvm-project/llvm/lib/Analysis/..