Displaying 3 results from an estimated 3 matches for "_7_iostream_error_category".
2015 Feb 10
2
[LLVMdev] llvm-link failing depending on order of files
...de directive is, however, required in
order to generate the error.)
llvm-link main.bc blank.bc works.
llvm-link blank.bc main.bc generates a linked object file that on
attempting to convert to an executable, gives the following error message:
a1.ll:30:1: error: unknown selection kind
$"\01??_7_Iostream_error_category at std@@6B@" = comdat
^
1 error generated.
(A slightly more complex test case gives a different error message at
earlier link time.)
Anyone have any idea about the cause of this and how to avoid it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://li...
2015 Feb 10
2
[LLVMdev] llvm-link deprecated in favor of gold plugin?
Ah! Okay. A quick test of llvm-lto gets an error:
llvm-lto: error adding file 'main.bc': Linking COMDATs named
'??_7_Iostream_error_category at std@@6B@': invalid selection kinds!
Would it be the case that llvm-lto is also deprecated in favor of the gold
plugin?
On Tue, Feb 10, 2015 at 4:47 PM, Teresa Johnson <tejohnson at google.com>
wrote:
> LTOCodeGenerator is used by the llvm-lto tool, which is a standalone
> tool...
2015 Feb 10
2
[LLVMdev] llvm-link deprecated in favor of gold plugin?
Following on from my last question, based on such information as I've been
able to find on Google, I get the impression llvm-link is effectively
deprecated / not actively maintained, because the focus of whole-program
optimization is now on the gold plugin. Is that the case, or am I missing
something?
Running searches over the source tree, it seems the Linker class that
actually implements