Displaying 4 results from an estimated 4 matches for "xx000".
Did you mean:
0x000
2020 Sep 29
3
OrcV1 removal
...t 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 like?
The other part that I am still missing is replacment for
LLVMCreateGDBRegistrationList...
2020 Sep 30
2
OrcV1 removal
...tly 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 like?
>
>
> We need an API to install an error reporter...
2013 Jul 01
3
Asterisk 1.8.20 AGI function SAY DATETIME does not play anything when mode in say.conf is changed to "new"
...9] => digits/${SAY:0:1}0, num:${SAY:1}
_[n]um:X00 => num:${SAY:0:1}, digits/hundred
_[n]um:XXX => num:${SAY:0:1}, digits/hundred, num:${SAY:1}
_[n]um:X000 => num:${SAY:0:1}, digits/thousand
_[n]um:XXXX => num:${SAY:0:1}, digits/thousand, num:${SAY:1}
_[n]um:XX000 => num:${SAY:0:2}, digits/thousand
_[n]um:XXXXX => num:${SAY:0:2}, digits/thousand, num:${SAY:2}
_[n]um:XXX000 => num:${SAY:0:3}, digits/thousand
_[n]um:XXXXXX => num:${SAY:0:3}, digits/thousand, num:${SAY:3}
_[n]um:X000000 => num:${SAY:0:1}, digits/million...
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