Displaying 8 results from an estimated 8 matches for "findsymbolin".
Did you mean:
findsymbol
2016 Apr 01
2
Kaleidoscope on Windows - bug maybe found?
...p
typedef ObjectLinkingLayer<> ObjLayerT;
C:\llvm\include\llvm\ExecutionEngine\Orc\ObjectLinkingLayer.h
JITSymbol findSymbol(StringRef Name, bool ExportedSymbolsOnly) {
for (auto I = LinkedObjSetList.begin(), E = LinkedObjSetList.end(); I
!= E;
++I)
if (auto Symbol = findSymbolIn(I, Name, ExportedSymbolsOnly))
return Symbol;
JITSymbol findSymbolIn(ObjSetHandleT H, StringRef Name,
bool ExportedSymbolsOnly) {
if (auto Sym = (*H)->getSymbol(Name)) {
C:\llvm\examples\Kaleidoscope\Orc\initial\toy.cpp
auto ExprSymbol = J.findUnman...
2016 Apr 01
0
Kaleidoscope on Windows - bug maybe found?
...; ObjLayerT;
>
> C:\llvm\include\llvm\ExecutionEngine\Orc\ObjectLinkingLayer.h
>
> JITSymbol findSymbol(StringRef Name, bool ExportedSymbolsOnly) {
> for (auto I = LinkedObjSetList.begin(), E = LinkedObjSetList.end(); I
> != E;
> ++I)
> if (auto Symbol = findSymbolIn(I, Name, ExportedSymbolsOnly))
> return Symbol;
>
> JITSymbol findSymbolIn(ObjSetHandleT H, StringRef Name,
> bool ExportedSymbolsOnly) {
> if (auto Sym = (*H)->getSymbol(Name)) {
> C:\llvm\examples\Kaleidoscope\Orc\initial\toy.cpp
>
&g...
2018 Sep 11
2
JIT tests on AArch64
...ngine/Orc/./OrcJITTests/RemoteObjectLayer.AddObjectFailure
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.EmitAndFinalizeFailure
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbol
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbolIn
LLVM-Unit :: ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.RemoveObjectFailure
2018 Sep 11
2
JIT tests on AArch64
...AddObjectFailure
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.EmitAndFinalizeFailure
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbol
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.FindSymbolIn
> LLVM-Unit ::
> ExecutionEngine/Orc/./OrcJITTests/RemoteObjectLayer.RemoveObjectFailure
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev...
2017 Feb 06
3
Kaleidoscope tutorial: comments, corrections and Windows support
...ymbolsOnly" and the exported flag seems to be implemented
incorrectly for COFF in LLVM (see bug report from Russell Wallace:
http://lists.llvm.org/pipermail/llvm-dev/2016-April/097964.html ).
Applied to the current version of Kaleidoscope, he suggested to use
"CompileLayer.findSymbolIn(H, Name, false)" in
"KaleidoscopeJIT::findMangledSymbol" to also allow non-exported
symbols.
I fixed it by changing "COFFObjectFile::getSymbolFlags" in
llvm-src/lib/Object/COFFObjectFile.cpp
to additionally OR SymbolRef::SF_Exported to Result:
> uint...
2015 Nov 23
2
COFF::IMAGE_REL_AMD64_REL32 relocation overflow when compiling for x86_64
...jectLinkingLayer<llvm::orc::DoNothingOnNotifyLoaded>::ConcreteLinkedObjectSet<std::shared_ptr<llvm::SectionMemoryManager>,ClangClasses::LLVMExecutionEngine::LinkingResolver
* __ptr64>::Finalize() Line 112 C++
llvm::orc::ObjectLinkingLayer<llvm::orc::DoNothingOnNotifyLoaded>::findSymbolIn::__l19::<lambda>()
Line 246 C++
std::_Callable_obj<unsigned __int64 <lambda>(void),0>::_ApplyX<unsigned
__int64>() Line 284 C++
std::_Func_impl<std::_Callable_obj<unsigned __int64
<lambda>(void),0>,std::allocator<std::_Func_class<unsigned __int64>
>...
2015 Nov 23
3
COFF::IMAGE_REL_AMD64_REL32 relocation overflow when compiling for x86_64
...:orc::DoNothingOnNotifyLoaded>::ConcreteLinkedObjectSet<std::shared_ptr<llvm::SectionMemoryManager>,ClangClasses::LLVMExecutionEngine::LinkingResolver
> * __ptr64>::Finalize() Line 112 C++
>
> llvm::orc::ObjectLinkingLayer<llvm::orc::DoNothingOnNotifyLoaded>::findSymbolIn::__l19::<lambda>()
> Line 246 C++
>
> std::_Callable_obj<unsigned __int64 <lambda>(void),0>::_ApplyX<unsigned
> __int64>() Line 284 C++
>
> std::_Func_impl<std::_Callable_obj<unsigned __int64
> <lambda>(void),0>,std::allocat...
2015 May 30
2
[LLVMdev] MCJit interface question
Agreed, that sounds like the best plan. I'll look into moving LLILC to ORC.
Thanks
-Joseph
From: Russell Hadley
Sent: Friday, May 29, 2015 8:13 PM
To: Lang Hames; Joseph Tremoulet
Cc: llvmdev at cs.uiuc.edu
Subject: RE: [LLVMdev] MCJit interface question
Hey Joseph,
What Lang said made me wonder. Is it the right time for us (LLILC) to move to ORC? The long term plan was to go there but