| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 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 |
Tags
- LLVM
- Android
- tracing
- pinpoint
- linux thread
- on-stack replacement
- 안티디버깅
- Injection
- on stack replacement
- Obfuscator
- anti debugging
- Linux packer
- pthread
- TLS
- LLVM 난독화
- apm
- linux debugging
- custom packer
- thread local storage
- LLVM Obfuscator
- tracerpid
- OSR
- android inject
- 난독화
- so inject
- Linux custom packer
- initial-exec
- v8 tracing
- uftrace
- v8 optimizing
Archives
- Today
- Total
Why should I know this?
byval 본문
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
'LLVM-STUDY' 카테고리의 다른 글
| SubclassOptionalData (0) | 2023.12.11 |
|---|---|
| computeKnownBits & KnownBits 관련 예제 (0) | 2023.12.05 |
| LLVM Study 관련 팁 (0) | 2023.10.25 |
| LLVM Pass 작성 - 2018년 이후 (0) | 2023.10.11 |
| Souper 분석 관련 키워드들 (0) | 2023.09.23 |
Comments