Displaying 10 results from an estimated 10 matches for "flagnames".
Did you mean:
flagname
2020 Apr 13
4
LLVM 10 ORC2 issue with symbol resolution
...leAndInterner mangle(*ES, *this->DL);
llvm::orc::SymbolMap Symbols;
for (int i = 0; global_syms[i].name != nullptr; i++) {
Symbols.insert({mangle(global_syms[i].name),
llvm::JITEvaluatedSymbol(llvm::pointerToJITTargetAddress(global_syms[i].address),
llvm::JITSymbolFlags(llvm::JITSymbolFlags::FlagNames::Absolute))});
}
llvm::cantFail(JD.define(llvm::orc::absoluteSymbols(Symbols)), "Failed
to install extern symbols");
FYI - my previous post on similar issue.
Basically I haven't been able to get ORC v2 working - tried in 8, 9 and now 10.
http://llvm.1065342.n5.nabble.com/llvm-dev-OR...
2020 Apr 13
2
LLVM 10 ORC2 issue with symbol resolution
...SymbolMap Symbols;
>> for (int i = 0; global_syms[i].name != nullptr; i++) {
>> Symbols.insert({mangle(global_syms[i].name),
>>
>> llvm::JITEvaluatedSymbol(llvm::pointerToJITTargetAddress(global_syms[i].address),
>>
>> llvm::JITSymbolFlags(llvm::JITSymbolFlags::FlagNames::Absolute))});
>> }
>> llvm::cantFail(JD.define(llvm::orc::absoluteSymbols(Symbols)), "Failed
>> to install extern symbols");
>>
>> FYI - my previous post on similar issue.
>> Basically I haven't been able to get ORC v2 working - tried in 8, 9 and n...
2013 Sep 17
0
[LLVMdev] [RFC] Internal command line options should not be statically initialized.
Wait, I have a terrible idea. Why don't we roll our own .init_array style
appending section? I think we can make this work for all toolchains we
support.
We'd have something like:
struct PODOptData {
const char *FlagName;
... // Common POD stuff, can be initialized at ParseCommandLine time.
};
LLVM_SECTION(".llvmopt")
PODOptData OptionRegisterer = { "foo_flag",
2019 Aug 14
3
ORC v2 question
Hi Lang,
On Tue, 13 Aug 2019 at 23:26, Lang Hames <lhames at gmail.com> wrote:
>> I also get this message:
>> JIT session error: Symbols not found: { raise_error }
>
>
> Ahh -- I see the problem. The DynamicLibrarySearchGenerator is using the getAddressOfSymbol method, which (under the hood) is basically issuing an appropriate dlsym lookup, and that does not find
2019 Nov 20
2
libunwind is not configured with -funwind-tables when building it for ARM Linux?
> On 18 Nov 2019, at 22:11, Peter Smith <peter.smith at linaro.org> wrote:
>
> On Mon, 18 Nov 2019 at 17:06, Sergej Jaskiewicz <jaskiewiczs at icloud.com <mailto:jaskiewiczs at icloud.com>> wrote:
>>
>>
>>
>> On 18 Nov 2019, at 19:55, Peter Smith <peter.smith at linaro.org> wrote:
>>
>> On Mon, 18 Nov 2019 at 15:23, Sergej
2020 Apr 13
2
LLVM 10 ORC2 issue with symbol resolution
...[i].name != nullptr; i++) {
> > >> Symbols.insert({mangle(global_syms[i].name),
> > >>
> > >>
> llvm::JITEvaluatedSymbol(llvm::pointerToJITTargetAddress(global_syms[i].address),
> > >>
> > >> llvm::JITSymbolFlags(llvm::JITSymbolFlags::FlagNames::Absolute))});
> > >> }
> > >> llvm::cantFail(JD.define(llvm::orc::absoluteSymbols(Symbols)), "Failed
> > >> to install extern symbols");
> > >>
> > >> FYI - my previous post on similar issue.
> > >> Basically I haven...
2013 Sep 17
11
[LLVMdev] [RFC] Internal command line options should not be statically initialized.
LLVM's internal command line library needs to evolve. We have an immediate need to build LLVM as a library free of static initializers, but before brute-force fixing this problem, I'd like outline the incremental steps that will lead to a desirable long term solution. We want infrastructure in place to provide an evolutionary path.
In the near term, clients who need llvm-the-library with
2013 Sep 17
3
[LLVMdev] [RFC] Internal command line options should not be statically initialized.
On Tue, Sep 17, 2013 at 11:29 AM, Reid Kleckner <rnk at google.com> wrote:
> Wait, I have a terrible idea. Why don't we roll our own .init_array style
> appending section? I think we can make this work for all toolchains we
> support.
>
Andy and I talked about this, but I don't think its worth it. My opinion is:
1. For tool options (the top-level llc, opt, llvm-as
2011 Jul 19
6
[PATCH 0/6] Move the infor for the help/man page in the source
The following series implement a way to generate the help messages and
the btrfs man page from the sources comments for the "btrfs" commanda
.
The syntax and the detailed help of every subcommand are stored in
the comments before the function which implements the subcommand.
The fact that the help messages and the man page are generated from the
same source should help to avoid
2019 Nov 18
2
libunwind is not configured with -funwind-tables when building it for ARM Linux?
> On 18 Nov 2019, at 19:55, Peter Smith <peter.smith at linaro.org> wrote:
>
> On Mon, 18 Nov 2019 at 15:23, Sergej Jaskiewicz <jaskiewiczs at icloud.com <mailto:jaskiewiczs at icloud.com>> wrote:
>>
>> Hi Peter,
>>
>> Thanks for your response.
>>
>> On 18 Nov 2019, at 17:44, Peter Smith <peter.smith at linaro.org> wrote: