Displaying 4 results from an estimated 4 matches for "easiyl".
Did you mean:
easily
2017 Aug 07
4
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...(maybe drop "-specifier" to make
it a bit more terse))
* clang option that maps to
* backend option (as currently)
* MCOption (programmatic/C++ API rather than command line of a backend
option)
* LLVM IR attribute on the CU (this feature could be supported on a
per-CU basis easiyl enough, thus survive LTO, etc, exactly as the user
requested (but really if the user requested this on at least one CU, they
probably might as well have it on all their CUs))
* LLVM IR module metadata
Any ideas/thoughts/other aspects?
-------------- next part --------------
An HTML attachment...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...to make
> it a bit more terse))
> * clang option that maps to
> * backend option (as currently)
> * MCOption (programmatic/C++ API rather than command line of a backend
> option)
> * LLVM IR attribute on the CU (this feature could be supported on a
> per-CU basis easiyl enough, thus survive LTO, etc, exactly as the user
> requested (but really if the user requested this on at least one CU, they
> probably might as well have it on all their CUs))
> * LLVM IR module metadata
>
>
> Any ideas/thoughts/other aspects?
>
>
>
--------------...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...to make
> it a bit more terse))
> * clang option that maps to
> * backend option (as currently)
> * MCOption (programmatic/C++ API rather than command line of a backend
> option)
> * LLVM IR attribute on the CU (this feature could be supported on a
> per-CU basis easiyl enough, thus survive LTO, etc, exactly as the user
> requested (but really if the user requested this on at least one CU, they
> probably might as well have it on all their CUs))
> * LLVM IR module metadata
>
>
> Any ideas/thoughts/other aspects?
>
-------------- next part...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...to make
> it a bit more terse))
> * clang option that maps to
> * backend option (as currently)
> * MCOption (programmatic/C++ API rather than command line of a backend
> option)
> * LLVM IR attribute on the CU (this feature could be supported on a
> per-CU basis easiyl enough, thus survive LTO, etc, exactly as the user
> requested (but really if the user requested this on at least one CU, they
> probably might as well have it on all their CUs))
> * LLVM IR module metadata
>
>
> Any ideas/thoughts/other aspects?
>
>
-------------- next...