Displaying 3 results from an estimated 3 matches for "pgextern".
Did you mean:
extern
2020 Sep 29
3
OrcV1 removal
...ame,
true, NULL);
else
addr = (uintptr_t) LLVMSearchForAddressOfSymbol(symname);
...
return (uint64_t) addr;
}
I don't think that can be implemented with the current C API.
Related to that, when hitting this case I currently get, on stderr:
JIT session error: Symbols not found: [ pgextern./home/andres/build/postgres/dev-assert/vpath/src/test/regress/regress.so.pt_in_widget ]
but currently that error is not bubbled up to the C API. There I just
get:
ERROR: XX000: failed to look up symbol "evalexpr_0_0": Failed to materialize symbols: { (main, { evalexpr_0_0 }) }
(obvious...
2020 Sep 30
2
OrcV1 removal
...ame (see example below), indicating that they should not be looked up
> > in the global namespace.
>
>
> From the example code I guess the namespacing for symbols from external
> libraries is something like: "<modulename>.<symbolname>" ?
It's currently pgextern.<path_to_library>.<symbolname>
> This is what definition generators are for. We can add an API for attaching
> generators and provide facilities to define a generator in C.
> Here you'd want a generator with a map of module names to dylib
> handles.
> First you'...
2020 Sep 24
2
OrcV1 removal
Hi All,
The Kaleidoscope tutorials have now been updated on the orcv1-removal
branch. I will try to summarise the state of the work and provide some
examples in the ORC JIT Weekly mailout tomorrow. The short version is that
I think this is ready to land on the mainline.
If anyone wants to check out the OrcV1 removal branch and provide feedback
now is the time. Otherwise I will aim to land the