Displaying 4 results from an estimated 4 matches for "rouschal".
2016 Jul 21
3
[llvm-toolchain v3.8.1] LTO: Linking clang hangs with ld.gold and LLVMgold.so plugin
Hi,
unfortunately, my build somehow hangs when linking clang binary and my
system is in an unusable state.
My toolchain is clang-3.8, gold-1.11 and LLVMgold.so from binutils
v2.26.1 (both selfmade) and LTO-flag is enabled.
My buildsystem uses cmake-3.6.0 and ninja-1.7.1 (both prebuilt).
I have 52 last steps left in my 3rd build.
My Linux-kernel is v3.13.0-92 from official Ubuntu repositories.
2016 Jul 23
2
[llvm-toolchain v3.8.1] LTO: Linking clang hangs with ld.gold and LLVMgold.so plugin
...]
> >
> > Now, I am able with backported LTO-flag from upstream to build with
> '-flto'.
> >
> > - EOT -
>
> Hi,
>
> in the meantime I tried with Linux v4.4.y LTS and 2GiB swap-space.
> So I have 4 GiB RAM and 2GiB SWAP in total 6GiB.
>
> Paul Rouschal recommended to reduce parallel-compile-jobs from 2 to 1...
>
> LLVM_PARALLEL_COMPILE_JOBS=1
> LLVM_PARALLEL_LINK_JOBS=1
>
> ...but that did not help.
>
> My Ubuntu/precise hangs and looking at top shows MEM/SWAP to be eaten.
>
> Anyone has experiences how much RAM or SWAP...
2016 Jul 23
3
[llvm-toolchain v3.8.1] LTO: Linking clang hangs with ld.gold and LLVMgold.so plugin
...ith
>>>> '-flto'.
>>>>
>>>> - EOT -
>>>
>>> Hi,
>>>
>>> in the meantime I tried with Linux v4.4.y LTS and 2GiB swap-space.
>>> So I have 4 GiB RAM and 2GiB SWAP in total 6GiB.
>>>
>>> Paul Rouschal recommended to reduce parallel-compile-jobs from 2 to 1...
>>>
>>> LLVM_PARALLEL_COMPILE_JOBS=1
>>> LLVM_PARALLEL_LINK_JOBS=1
>>>
>>> ...but that did not help.
>>>
>>> My Ubuntu/precise hangs and looking at top shows MEM/SWAP to be e...
2018 Jan 26
1
RFC: Using link-time optimization to eliminate retpolines
Hi,
Sean Silva via llvm-dev wrote:
> Wouldn't a branch funnel open the door to a type 1 attack?
Only if the code looks exactly as you wrote it. If I understand this
correctly the problem with indirect branches is that the "gadget", the
code leaking the data, could be *anywhere* in the binary, giving the
attacker much more freedom. So restricting these calls to one of the