Displaying 3 results from an estimated 3 matches for "ld_plugin_input_fil".
Did you mean:
ld_plugin_input_file
2016 Apr 20
2
Dead (or untested?) code in the gold plugin
...d-plugin.cpp
@@ -428,8 +428,6 @@ getMinVisibility(GlobalValue::VisibilityTypes A,
return A;
if (B == GlobalValue::HiddenVisibility)
return B;
- if (A == GlobalValue::ProtectedVisibility)
- return A;
return B;
}
@@ -520,15 +518,9 @@ static ld_plugin_status claim_file_hook(const
ld_plugin_input_file *file,
Res.IsLinkonceOdr &= GV->hasLinkOnceLinkage();
Res.Visibility = getMinVisibility(Res.Visibility, GV->getVisibility());
switch (GV->getVisibility()) {
- case GlobalValue::DefaultVisibility:
- sym.visibility = LDPV_DEFAULT;
- break;...
2010 Oct 05
3
[LLVMdev] problems configuring LLVM with gold plugin
...7:2:
error: #error can not find uint64_t type
In file included from gold-plugin.cpp:15:
/home/lefever/work/llvm/v2.6/llvm-2.6_optimized/../gold-plugin/binutils/src/include/plugin-api.h:91:
error: ‘uint64_t’ does not name a type
gold-plugin.cpp: In function ‘ld_plugin_status claim_file_hook(const
ld_plugin_input_file*, int*)’:
gold-plugin.cpp:279: error: ‘struct ld_plugin_symbol’ has no member
named ‘size’
make[2]: ***
[/home/lefever/work/llvm/v2.6/llvm-2.6_optimized/tools/gold/Release/gold-plugin.o]
Error 1
--------------------------
Thanks,
Ryan
2011 Feb 24
0
[LLVMdev] MemoryBuffer and its requirement for NULL termination
...for some cases. For
example, currently I get the following valgrind error when doing LTO and
fetching an archive member:
at 0x6DAC36E: llvm::MemoryBuffer::init(char const*, char const*)
(MemoryBuffer.cpp:50)
Address 0x5fecea0 is 0 bytes after a block of size 464 alloc'd
claim_file_hook(ld_plugin_input_file const*, int*) (gold-plugin.cpp:261)
The memory access is the assert that the buffer is null terminated and
the allocation is done to read in an archive member to pass to libLTO.
I could fix this by just allocating one byte more, but I would like
instead to mmap the archives. There is no way to...