Displaying 6 results from an estimated 6 matches for "searchorder".
2020 Apr 16
4
ORC Assertion failure
...) Line
2188 C++
libravi.dll!llvm::orc::ExecutionSession::lookup(llvm::orc::LookupKind
K, const std::vector<std::pair<llvm::orc::JITDylib *,enum
llvm::orc::JITDylibLookupFlags>,std::allocator<std::pair<llvm::orc::JITDylib
*,enum llvm::orc::JITDylibLookupFlags>>> & SearchOrder,
llvm::orc::SymbolLookupSet Symbols, llvm::orc::SymbolState
RequiredState, llvm::unique_function<void
__cdecl(llvm::Expected<llvm::DenseMap<llvm::orc::SymbolStringPtr,llvm::JITEvaluatedSymbol,llvm::DenseMapInfo<llvm::orc::SymbolStringPtr>,llvm::detail::DenseMapPair<llvm::orc::Symb...
2014 Dec 15
1
Using of pxelinux configfiles for both BIOS and UEFI boot
...nux.efi in efi64 mode)
If I remove/rename the bootloader ldlinux.e64 the seachorder for efi is:
Ldlinux.e64
/ldlinux.e64
/boot/isolinux/ldlinux.e64
/isolinux/ldlinux.e64
/boot/syslinux/ldlinux.e64
/syslinux/ldlinux.e64
/ldlinux.e64
If I remove/rename the configfile pxelinux.cfg/default the searchorder for efi is:
pxelinux.cfg/uuid (or something similar)
pxelinux.cfg/macaddress
...
pxelinux.cfg/(parts of macaddress)
...
pxelinux.cfg/default
and then the boot fails with a "configuration file not found" error.
Peter
2020 Mar 18
4
[ORC JIT] -Resolving cross references in a multi-process scenario
...to use orc::SymbolState::Resolved, which will cause the
query to return as soon as the searched-for symbols have been assigned an
address.
So if your process is generating a set of symbols that may need to be
transmitted to other sessions then you would write something like:
auto Syms = ES.lookup(SearchOrder, SymbolsToTransmit, LookupKind::Static,
SymbolState::Resolved);
if (!Syms)
reportError(Syms.takeError());
sendSymbolsToRemote(*Syms);
Out of interest -- Is it necessary for your JIT itself to be split across
two or more processes? I had always anticipated having a single
ExecutionSession attache...
2014 Dec 12
0
Using of pxelinux configfiles for both BIOS and UEFI boot
>I could be wrong about this, but... I think that it could still be possible to get multiple architectures / firmwares mixed together >while using c32 modules, without dhcp options, and perhaps even without applying pxelinux-options.
>
>If I understood correctly, this tftp server can choose between 2 boot files, depending on BIOS/UEFI client, and the problem is >choosing a
2014 Dec 11
2
Using of pxelinux configfiles for both BIOS and UEFI boot
> On Mon, Dec 8, 2014 at 10:44 AM, Leenders, Peter
> <Peter.Leenders at computacenter.com> wrote:
>
> > This look promising, if I could separate the config files for the different
> > boot architectures Bios and UEFI. I have 2 different boot files in 2
> > different locations, but after startup they both refer to the
> > tftproot/pxlinux.cfg/default config
2020 Mar 06
2
[ORC JIT] -Resolving cross references in a multi-process scenario
Hello LLVM-Mailing-List and Lang,
I have a very weird (or strict?) scenario and was curious if the ORC JIT can help me with it. Soo here it comes:
I have currently a windows process ("Runtime") which does nothing but creating a shared memory with read, write and execute rights - and also writing some function addresses like from printf to it.
Then I have two or more processes which