[llvm] [BOLT] Enable hugify for AArch64 (PR #117158)

[via llvm-commits]

================
@@ -11,17 +11,28 @@ int main(int argc, char **argv) {
 REQUIRES: system-linux,bolt-runtime
 
 RUN: %clang %cflags -no-pie %s -o %t.nopie.exe -Wl,-q
-RUN: %clang %cflags -fpic -pie %s -o %t.pie.exe -Wl,-q
----------------
alekuz01 wrote:

Sure! You may ask. I hope I could respond to this comment with the following explanation: 
* llvm uses lit for testing
* lit has its own configuration files, for example lit.local.cfg (bolt/runtime, bolt/test)
* if you can check those files you can find there: `-pie -fPIE` flags. Those flags are applied to the mentioned binary by default. Except `-fpic`.

```
+ bin/clang --target=aarch64-unknown-linux-gnu -fPIE -fuse-ld=lld -Wl,--unresolved-symbols=ignore-all -Wl,--build-id=none -pie llvm-project/bolt/test/runtime/hugify.c -o tools/bolt/test/runtime/Output/hugify.c.tmp.pie.exe -Wl,-q
```

I think your question is about whether to use `-fpic`or not in this case as `-pie` is used by default? 

```
+ bin/clang --target=aarch64-unknown-linux-gnu -fPIE -fuse-ld=lld -Wl,--unresolved-symbols=ignore-all -Wl,--build-id=none -pie -fpic /llvm-project/bolt/test/runtime/hugify.c -o tools/bolt/test/runtime/Output/hugify.c.tmp.pie.exe -Wl,-q 
```

Should we discuss what exactly `-fpic` would check here? Would it affect the output of nm?

https://github.com/llvm/llvm-project/pull/117158