Displaying 7 results from an estimated 7 matches for "modk".
Did you mean:
mode
2015 Jul 18
2
[LLVMdev] [Clang] [lld] [llvm-link] Whole program / dead-code optimization
...ogram flag in clang. Perhaps this is not even possible?
If I can't get any answers here I may repost that specific question since I
didn't list [opt] in the original question subject.
Thanks,
Ed
On Fri, Jul 17, 2015 at 1:15 AM, Nick Lewycky <nicholas at mxc.ca> wrote:
> ed at modk.it wrote:
>
>>
>> Is there a reason why LLVM's link-time optimization won't work for
>> you?
>>
>> http://llvm.org/docs/GoldPlugin.html
>> <
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__llvm.org_docs_GoldPlugin.html&d...
2015 Jul 06
2
[LLVMdev] [lld] Current ways to position memory sections (e.g. .text, .data, .bss) with lld?
...gnSectionsToSegments() works and go from there.
> This function lives at lld/lib/ReaderWriter/ELF/TargetLayout.cpp. I don't
> believe you can try any other flags to try to get this done without fixing
> this logic.
>
> Rafael Auler
>
> On Wed, Jul 1, 2015 at 12:00 PM, ed at modk.it <ed at modk.it> wrote:
>
>> Hi All,
>>
>> Congratulations on the major progress on the llvm linker lld over the
>> past year including the new linker script support. This really makes it
>> possible to ditch binutils altogether. It looks like lld's ME...
2015 Jul 01
2
[LLVMdev] [lld] Current ways to position memory sections (e.g. .text, .data, .bss) with lld?
Hi All,
Congratulations on the major progress on the llvm linker lld over the past
year including the new linker script support. This really makes it
possible to ditch binutils altogether. It looks like lld's MEMORY sections
are currently parsed but not evaluated, but so far that hasn't been a
problem.
The only snag is I can't figure out how to define the start of the .data
section
2015 Jul 15
4
[LLVMdev] [Clang] Reasons for lack of -fsingle-precision-constant support? Alternatives?
Hi All,
Clang lacks support for the -fsingle-precision-constant flag. Are there
specific reasons for this or is it just waiting to be implemented?
This flag is especially important in the embedded world. From
http://processors.wiki.ti.com/index.php/Floating_Point_Optimization#float_vs._double_vs._long_double
:
*Once all of your data is defined as float, there are still cases where you
may
2015 Jul 16
2
[LLVMdev] [Clang] [lld] [llvm-link] Whole program / dead-code optimization
>
>
> Is there a reason why LLVM's link-time optimization won't work for you?
>
> http://llvm.org/docs/GoldPlugin.html
> http://llvm.org/docs/LinkTimeOptimization.html
>
>
Well the primary motivation to move to LLVM is licensing which is why we
also ditched binutils since we can't package gcc for iOS due to the GPL.
So in the end the gold plugin wouldn't
2015 Jul 15
2
[LLVMdev] [Clang] Reasons for lack of -fsingle-precision-constant support? Alternatives?
Thanks for the response. If we add the support would you accept the
patch? Seems like a pretty straightforward flag since it maps directly to
NumericLiteralParser::NumericLiteralParser within LiteralSupport.cpp. I
understand the maintenance concern with flags that affect multiple points
in code though.
Still trying to get the bottom of why we're crashing with double floating
point literal.
2015 Jul 16
2
[LLVMdev] [Clang] [lld] [llvm-link] Whole program / dead-code optimization
Hi All,
After the initial learning curve, we're excited to have put together a
completely gcc/binutils-free toolchain based on LLVM. Now that we have
things working, we desperately need to optimize the resulting binaries.
Our bin files are up to 10x their fully optimized gcc equivalent (1.5k vs
16k). This is for a bare metal ARM based system so this is significant.
We're using lld for