Displaying 4 results from an estimated 4 matches for "transferto".
Did you mean:
transfert
2020 Sep 16
4
OrcV1 removal
...izationUnit to
a JITDylib (with JITDylib::define, or a Layer's add method) you can
optionally specify a tracker to associate with that unit. If no tracker is
specified the default tracker for the target JITDylib will be used. A
single tracker can be associated with multiple units the remove and
transferTo operations (see below) will apply to all associated units.
You can call ResourceTracker::remove at any time to remove all symbols and
resources associated with a tracker. Any active compiles associated with
the tracker will receive an error when they try to update the JIT state via
their Materiali...
2020 Sep 24
2
OrcV1 removal
...ylib::define, or a Layer's add method) you can
>> optionally specify a tracker to associate with that unit. If no tracker is
>> specified the default tracker for the target JITDylib will be used. A
>> single tracker can be associated with multiple units the remove and
>> transferTo operations (see below) will apply to all associated units.
>>
>> You can call ResourceTracker::remove at any time to remove all symbols
>> and resources associated with a tracker. Any active compiles associated
>> with the tracker will receive an error when they try to updat...
2020 Sep 07
2
OrcV1 removal
Hi Andres,
Postgres uses removable code support and Orcv1. I does make me quite
> worried to see a phase where there'll be no viable way of using both in
> llvm. Why isn't the right answer here to at lest develop the
> replacement as a set of patches / as a branch that then can be merged as
> a whole / shortly after each other, rather than just starting to develop
> a
2020 Sep 16
2
OrcV1 removal
...iated with
> > the tracker will receive an error when they try to update the JIT state
> via
> > their MaterializationResponsibility, and will not be able to associate
> > resources with the tracker's associated ResourceKey.
> >
> > You can call ResourceTracker::transferTo at any time. This will transfer
> > tracking of all associated symbols and resources to the destination
> > tracker. Any active compiles associated with the tracker will be
> > reassociated with the destination tracker, and all future resources will
> be
> > associated wi...