Displaying 10 results from an estimated 10 matches for "rouban".
2018 Nov 06
2
[RFC] Enable thread specific cl::opt values for multi-threaded support
...objects be responsible for options rather than thread-local storage, but in order to not break how cl::opt works today we need an answer to the initialization story. Maybe per-library initialization? We already have that for most of our libraries.
-Chris
> On Oct 31, 2018, at 12:11 AM, Yevgeny Rouban via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> >>! In D53424#1273950 <tel:1273950>, @delcypher wrote:
> >>>! In D53424#1273737 <tel:1273737>, @yrouban wrote:
> >>>>! In D53424#1273728 <tel:1273728>, @jfb wrote:
> >>>...
2018 Mar 29
0
Opt Bisect layering
...be bisecting over multiple
LLVMContexts? & even then, maybe it'd be more suitable for that grouping
(the scope for the bisection) to be API driven - passing the bisector into
the LLVMContext ctor to define the set of contexts that share a bisector?
On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Andrew,
>
> I would not make the caller pass the description of the IR unit. That is
> because it would result in the description generated every time even if
> OptBisect is disabled. Description generation is not very chip....
2018 Mar 22
2
Opt Bisect layering
...because it would result in the description generated every time even if
OptBisect is disabled. Description generation is not very chip.
Thinking on the OptBisect extension, I believe passing the units are the
right choice because OptPassGates may use them to make pass skipping
decisions.
-Yevgeny Rouban
-----------------------------------------------------------
*From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org
<llvm-dev-bounces at lists.llvm.org>] *On Behalf Of *Kaylor, Andrew via llvm-
dev
*Sent:* Thursday, March 22, 2018 3:52 AM
*To:* David Blaikie <dblaikie at gmail.com>...
2018 Mar 29
2
Opt Bisect layering
...ple
> LLVMContexts? & even then, maybe it'd be more suitable for that grouping
> (the scope for the bisection) to be API driven - passing the bisector into
> the LLVMContext ctor to define the set of contexts that share a bisector?
>
> On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Andrew,
>>
>> I would not make the caller pass the description of the IR unit. That is
>> because it would result in the description generated every time even if
>> OptBisect is disabled. Description...
2018 Apr 03
0
Opt Bisect layering
...multiple LLVMContexts? & even then, maybe it'd be more
suitable for that grouping (the scope for the bisection) to be API
driven - passing the bisector into the LLVMContext ctor to define the
set of contexts that share a bisector?
>
> On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Andrew,
>
> I would not make the caller pass the description of the IR
unit. That is because it would result in the description generated every
time even if OptBisect is disabled. Description generation is...
2018 Apr 03
2
Opt Bisect layering
...? & even then, maybe it'd be more
> suitable for that grouping (the scope for the bisection) to be API
> driven - passing the bisector into the LLVMContext ctor to define the
> set of contexts that share a bisector?
> >
> > On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> >
> > Andrew,
> >
> > I would not make the caller pass the description of the IR
> unit. That is because it would result in the description generated every
> time even if OptBisect is dis...
2018 Apr 03
0
Opt Bisect layering
...it'd be more
> suitable for that grouping (the scope for the bisection) to be API
> driven - passing the bisector into the LLVMContext ctor to define the
> set of contexts that share a bisector?
> >
> > On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> >
> > Andrew,
> >
> > I would not make the caller pass the description of the IR
> unit. That is because it would result in the description
generated every
&g...
2018 Apr 03
2
Opt Bisect layering
...suitable for that grouping (the scope for the bisection) to be API
> > driven - passing the bisector into the LLVMContext ctor to define
> the
> > set of contexts that share a bisector?
> > >
> > > On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> > >
> > > Andrew,
> > >
> > > I would not make the caller pass the description of the
> IR
> > unit. That is because it would result in t...
2018 May 03
2
Opt Bisect layering
...bisection) to be API
> > driven - passing the bisector into the LLVMContext ctor
> to define the
> > set of contexts that share a bisector?
> > >
> > > On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban
> via llvm-dev
> > <llvm-dev at lists.llvm.org
> <mailto:llvm-dev at lists.llvm.org>> wrote:
> > >
> > > Andrew,
> > >
> > > I would not m...
2018 Apr 23
0
Opt Bisect layering
...grouping (the scope for the bisection) to be API
>> > driven - passing the bisector into the LLVMContext ctor to define
>> the
>> > set of contexts that share a bisector?
>> > >
>> > > On Wed, Mar 21, 2018 at 10:20 PM Yevgeny Rouban via llvm-dev
>> > <llvm-dev at lists.llvm.org> wrote:
>> > >
>> > > Andrew,
>> > >
>> > > I would not make the caller pass the description of the
>> IR
>> > unit. That is...