search for: pt_in_widget

...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 }) } (obviously the first part is postgres code) Do you have thoughts on what that should look lik...

...already exist) then you'd dlsym <symbolname> in that handle. Ok, cool. > 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 }) } > > (obviously the first part is postgr...

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