일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
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 |
- Injection
- so inject
- LLVM 난독화
- v8 optimizing
- LLVM
- Linux packer
- v8 tracing
- linux debugging
- Linux custom packer
- custom packer
- tracerpid
- 안티디버깅
- uftrace
- android inject
- tracing
- on-stack replacement
- linux thread
- 난독화
- initial-exec
- TLS
- anti debugging
- thread local storage
- on stack replacement
- Android
- Obfuscator
- pthread
- LLVM Obfuscator
- pinpoint
- OSR
- apm
- Today
- Total
목록전체 글 (141)
Why should I know this?
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/..
https://llvm.org/devmtg/2016-11/Slides/Finkel-IntrinsicsMetadataAttributes.pdf
https://llvm.org/docs/MemorySSA.html MemorySSA — LLVM 18.0.0git documentation MemorySSA is an analysis that can be built for any arbitrary function. When it’s built, it does a pass over the function’s IR in order to build up its mapping of MemoryAccesses. You can then query MemorySSA for things like the dominance relation betwee llvm.org
1. 당면한 문제에 `몰입`도 중요하지만 더 큰 구조를 생각하는 것도 중요하다. 제가 경험했던 패치 https://reviews.llvm.org/D153752 ⚙ D153752 [InstSimplify] Fold icmp comparing GEPs with local allocation This revision is now accepted and ready to land. reviews.llvm.org 최근에 살펴본 패치 https://die4taoam.tistory.com/136 [InstSimplify] Fold (a != 0) ? abs(a) : 0 https://github.com/llvm/llvm-project/pull/70305 [InstSimplify] Fold (a != 0) ? abs(a..
이번에 살펴볼 패치는 매우 짧아서 좋은 패치 입니다. 패치의 링크 https://github.com/llvm/llvm-project/issues/71183 Memcpyopt crashes with simple IR · Issue #71183 · llvm/llvm-project target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128-ni:10:11:12:13" target triple = "x86_64-unknown-linux-gnu" define void @"julia_#36#f_439"() { top: call v... github.com 최초에 문제가 발생하는 IR 은 다음과 같습니다. def..