Displaying 13 results from an estimated 13 matches for "elftyp".
Did you mean:
elftype
2018 Jul 25
2
are the LLD libraries thread safe?
...ld::elf::SymbolTable::insert(llvm::StringRef)
(SymbolTable.cpp:225)
==5467== by 0x516A21: lld::elf::SymbolTable::insert(llvm::StringRef,
unsigned char, unsigned char, bool, lld::elf::InputFile*)
(SymbolTable.cpp:260)
==5467== by 0x51B88C: void
lld::elf::SymbolTable::addShared<llvm::object::ELFType<(llvm::support::endianness)1,
true> >(llvm::StringRef,
lld::elf::SharedFile<llvm::object::ELFType<(llvm::support::endianness)1,
true> >&, llvm::object::ELFType<(llvm::support::endianness)1, true>::Sym
const&, unsigned int, unsigned int) (SymbolTable.cpp:483)
==54...
2018 Jul 25
2
are the LLD libraries thread safe?
...(SymbolTable.cpp:225)
>> ==5467== by 0x516A21: lld::elf::SymbolTable::insert(llvm::StringRef,
>> unsigned char, unsigned char, bool, lld::elf::InputFile*)
>> (SymbolTable.cpp:260)
>> ==5467== by 0x51B88C: void lld::elf::SymbolTable::addShar
>> ed<llvm::object::ELFType<(llvm::support::endianness)1, true>
>> >(llvm::StringRef, lld::elf::SharedFile<llvm::obj
>> ect::ELFType<(llvm::support::endianness)1, true> >&,
>> llvm::object::ELFType<(llvm::support::endianness)1, true>::Sym const&,
>> unsigned int, uns...
2016 Nov 08
2
leaks in lld on the bot
...s
Direct leak of 184 byte(s) in 1 object(s) allocated from:
#0 0x72fab0 in operator new(unsigned long)
/mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:82
#1 0x8c8610 in void
lld::elf::BinaryFile::parse<llvm::object::ELFType<(llvm::support::endianness)1,
true> >() /mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/tools/lld/ELF/InputFiles.cpp:823:7
#2 0xb9de74 in
lld::elf::SymbolTable<llvm::object::ELFType<(llvm::support::endianness)1,
true> >::addFile(lld::elf::InputFile*)...
2016 Nov 08
3
leaks in lld on the bot
...bject(s) allocated from:
>> #0 0x72fab0 in operator new(unsigned long)
>> /mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:82
>> #1 0x8c8610 in void
>> lld::elf::BinaryFile::parse<llvm::object::ELFType<(llvm::support::endianness)1,
>> true> >()
>> /mnt/b/sanitizer-buildbot2/sanitizer-x86_64-linux-bootstrap/build/llvm/tools/lld/ELF/InputFiles.cpp:823:7
>> #2 0xb9de74 in
>> lld::elf::SymbolTable<llvm::object::ELFType<(llvm::support::endianness)1,
>>...
2017 Mar 23
6
[RFC] better link error messages
...e informative and easy to read.
Below are examples of the current error messages (note that characters in
red are actually red on terminal):
*Undefined symbols*
/ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207:
undefined symbol 'lld::elf::EhFrameSection<llvm
::object::ELFType<(llvm::support::endianness)0, true>
>::addSection(lld::elf::InputSectionBase*)'
*Conflicting symbols*
/ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:38:
duplicate symbol 'lld::elf::MipsGotSection::addEntry(lld::elf::SymbolBody&,
long, lld::elf::RelExpr)...
2017 Mar 29
2
[RFC] better link error messages
..., the following error messages should work for
> everybody. I'll create a patch to make this change and send it for
> review. Thank you guys for the inputs!
>
>
> Undefined symbol error:
>
> bin/ld.lld: error: undefined symbol:
> lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0,
> true>
> *>>> defined at* Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207)
> *>>>* Writer.cpp.o in archive lib/liblldELF.a
The wording of this one is mildly self contradictory. Undefined symbols
aren't define...
2017 Mar 29
2
[RFC] better link error messages
...the new format
looks awesome!
Thanks,
Rafael
On 29 March 2017 at 15:18, Rui Ueyama via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> My bad. I intended this.
>
> Undefined symbol error:
>
> bin/ld.lld: error: undefined symbol:
> lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0,
> true>
>>>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207)
>>>> Writer.cpp.o in archive lib/liblldELF.a
>
>
> Duplicate symbol error:
>
> bin/ld.lld: error: duplicate symbol:
>...
2017 Mar 24
4
[RFC] better link error messages
...`) are still a bit easier to parse in
> the presence of wrapped lines.
>
Makes sense. I tried a few different formats based on suggestions from
Mehdi, Hans and you, and come up with this one. What do you think?
bin/ld.lld: *error:* undefined symbol:
lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0,
true> >::addSection(lld::elf::InputSectionBase*)
*>>> referenced by*
/home/buildslave/buildslave/clang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207
*>>>* lib/liblldELF.a(Writer.cpp.o)
bin/ld.lld: *error:* duplicate s...
2017 Mar 29
3
[RFC] better link error messages
...apped lines.
>>>
>>
>> Makes sense. I tried a few different formats based on suggestions from
>> Mehdi, Hans and you, and come up with this one. What do you think?
>>
>> bin/ld.lld: *error:* undefined symbol: lld::elf::EhFrameSection<llvm:
>> :object::ELFType<(llvm::support::endianness)0, true>
>> >::addSection(lld::elf::InputSectionBase*)
>> *>>> referenced by* /home/buildslave/buildslave/cl
>> ang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207
>> *>>>* lib/liblldELF.a(Writer.cpp....
2017 Mar 25
4
[RFC] better link error messages
...>> the presence of wrapped lines.
>>
>
> Makes sense. I tried a few different formats based on suggestions from
> Mehdi, Hans and you, and come up with this one. What do you think?
>
> bin/ld.lld: *error:* undefined symbol: lld::elf::EhFrameSection<llvm:
> :object::ELFType<(llvm::support::endianness)0, true>
> >::addSection(lld::elf::InputSectionBase*)
> *>>> referenced by* /home/buildslave/buildslave/cl
> ang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207
> *>>>* lib/liblldELF.a(Writer.cpp.o)
>
>
>...
2019 Mar 19
2
AArch64 tests failing
...00ffff9edac6c0 (linux-vdso.so.1+0x6c0)
#4 0x000000000042a098 std::_Function_handler<bool (llvm::objcopy::elf::SectionBase const&), llvm::objcopy::elf::handleArgs(llvm::objcopy::CopyConfig const&, llvm::objcopy::elf::Object&, llvm::objcopy::elf::Reader const&, llvm::objcopy::elf::ElfType)::'lambda2'(llvm::objcopy::elf::SectionBase const&)>::_M_invoke(std::_Any_data const&, llvm::objcopy::elf::SectionBase const&) (/clang/build/aarch64/bin/llvm-objcopy+0x42a098)
#5 0x0000000000432ca8 llvm::objcopy::elf::Object::removeSections(std::function<bool (llvm::objc...
2019 May 10
2
contributing llvm-lipo
...te:
> I think that pretty much hits the nail on the head. The llvm-objcopy code
> is for when you need to perform mutations primarily. A common mistake (well
> a mistake in my opinion) I see is people wanting a one size fits all
> solution when one doesn't exist (or perhaps rather, ELFTypes is as close as
> we have). As long as we conclude that kind of mutative model fits well here
> then we should proceed. That's what I left all the cryptic "if this really
> fits into the llvm-objcopy model" messages.
>
> *From: *Alexander Shaposhnikov <alexander.v.s...
2019 May 10
2
contributing llvm-lipo
Hi Jake,
many thanks,
yea, I have very similar feelings / thoughts.
After some thinking it seems to me that this discussion/problem which I
have brought up is, in fact,
more relevant to the tools which really need a robust mutable model of an
object file (like objcopy, strip, install_name_tool, etc),
but the particular case of "lipo" might be simpler, I need to double check
that / will