search for: subthread

(This subthread is more appropriate to -users than to -dev, so it is crossposted only to mark its transition. Please reply on the -user list only.) What are the cheapest prices for (humans) transcribing voicemail to text as a service? The absolute cheapest, regardless of (known) quality - the quality only has to...

...ndex dfc357614e56..958d2972313f 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -126,7 +126,7 @@ static bool oom_cpuset_eligible(struct task_struct *tsk, struct oom_control *oc) /* * The process p may have detached its own ->mm while exiting or through - * use_mm(), but one or more of its subthreads may still have a valid + * kthread_use_mm(), but one or more of its subthreads may still have a valid * pointer. Return p, or any of its subthreads with a valid ->mm, with * task_lock() held. */ @@ -919,8 +919,8 @@ static void __oom_kill_process(struct task_struct *victim, const char *me...

...ndex dfc357614e56..958d2972313f 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -126,7 +126,7 @@ static bool oom_cpuset_eligible(struct task_struct *tsk, struct oom_control *oc) /* * The process p may have detached its own ->mm while exiting or through - * use_mm(), but one or more of its subthreads may still have a valid + * kthread_use_mm(), but one or more of its subthreads may still have a valid * pointer. Return p, or any of its subthreads with a valid ->mm, with * task_lock() held. */ @@ -919,8 +919,8 @@ static void __oom_kill_process(struct task_struct *victim, const char *me...

...re remarked available_externally. For a non-discardable symbol that was imported, we can discard here since we are done with inlining (it is non-discardable in its home module)." &, like Duncan, I'll wait for more details on that front. (may or may not be useful to split some of these subthreads into separate email threads to keep discussion clear - but I'm not sure) > > > - David > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150515/b6ba7050/attachment.html>

I'm a bit confused by this subthread -- doesn't BOLT have the exact same CFI bloat issue? From my cursory reading of the propellor doc, the CFI duplication is _necessary_ to represent discontiguous functions, not anything particular to the way Propellor happens to generate those discontiguous functions. And emitting discontiguous...

...gt; have to say that on the reassociation point, my concern is that to > really suppress that, we will have to suppress so much, that there will > hardly be any point in using -ffast-math. > > > > I'd say your comments here are very similar to what Nicolai said in > another subthread of this discussion: > > > >>> I'd be really curious to know if there is anybody who really needs arcp > >>> without fp-contract=fast or vice versa, or who needs both of these but > >>> not the X*log2(0.5*Y) transform you mentioned, and so on.[1] > &g...

...discardable symbol that was imported, we can discard here since we > > are done with inlining (it is non-discardable in its home module)." > > > > &, like Duncan, I'll wait for more details on that front. (may or may > not be > > useful to split some of these subthreads into separate email threads to > keep > > discussion clear - but I'm not sure) > > I just went back and looked at my prototype and I had remembered this > wrong. An imported function is always marked > AvailableExternallyLinkage, unless it has link once linkage. > >...

...have to say that on the reassociation point, my concern is that to > really suppress that, we will have to suppress so much, that there will > hardly be any point in using -ffast-math. > > > > I'd say your comments here are very similar to what Nicolai said in > another subthread of this discussion: > > > > I'd be really curious to know if there is anybody who really needs arcp > > without fp-contract=fast or vice versa, or who needs both of these but > > not the X*log2(0.5*Y) transform you mentioned, and so on.[1] > > ... > >...

> On Dec 1, 2014, at 3:44 PM, Philip Reames <listmail at philipreames.com> wrote: > > (Spawning a separate subthread off the 'Optimization hints for "constant" loads' discussion for a related question. ) > > Looking at TBAA again, I was reminded that TBAA also contains a third field which indicates that "meaning pointsToConstantMemory should return true; see other useful AliasAnalysi...

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

...; twice... even if that doesn't actually conflict with the required > semantics of READ_ONCE(), it looks odd. It's patched at runtime, so it's either LDAR or LDAPR. > Making a direct link between LTO and the memory model also seems highly > spurious (as discussed in the other subthread) so can we have a comment > explaining the reasoning? Sure, although like I say, this is more about helping to progress that conversation. Will

(This subthread is more appropriate to -users than to -dev, so it is crossposted only to mark its transition. Please reply on the -user list only.) What are the cheapest prices for (humans) transcribing voicemail to text as a service? The absolute cheapest, regardless of (known) quality - the quality only has to...

...e we could rewrite it compactly like BOLT. > These would help with object size bloats and binary size bloats. > > > > > > On Wed, Oct 2, 2019 at 1:59 PM James Y Knight via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > I'm a bit confused by this subthread -- doesn't BOLT have the exact same CFI bloat issue? From my cursory reading of the propellor doc, the CFI duplication is _necessary_ to represent discontiguous functions, not anything particular to the way Propellor happens to generate those discontiguous functions. > > > > And emi...

...ern is that to >>> really suppress that, we will have to suppress so much, that there will >>> hardly be any point in using -ffast-math. >>> >>> >>> >>> I'd say your comments here are very similar to what Nicolai said in >>> another subthread of this discussion: >>> >>> >>> >>> I'd be really curious to know if there is anybody who really needs arcp >>>>> >>>> >>> without fp-contract=fast or vice versa, or who needs both of these but >>>>> >>...

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API.

...dev->phys = vi->phys; > > + vi->idev->id.bustype = BUS_VIRTUAL; > > + vi->idev->id.vendor = 0x0001; > > + vi->idev->id.product = 0x0001; > > + vi->idev->id.version = 0x0100; > > Add comments explaining why these #s make sense? See other subthread, will be changed to be host-provided (like name). > > + err = input_register_device(vi->idev); > > Once you do this, virtinput_status can get called, > and that will kick, correct? Correct. > If so, you must call device_ready before this. Ok. > > + if (err) > &gt...

...dev->phys = vi->phys; > > + vi->idev->id.bustype = BUS_VIRTUAL; > > + vi->idev->id.vendor = 0x0001; > > + vi->idev->id.product = 0x0001; > > + vi->idev->id.version = 0x0100; > > Add comments explaining why these #s make sense? See other subthread, will be changed to be host-provided (like name). > > + err = input_register_device(vi->idev); > > Once you do this, virtinput_status can get called, > and that will kick, correct? Correct. > If so, you must call device_ready before this. Ok. > > + if (err) > &gt...

Apply the ideas in the previous patch to the C-language bindings generator. Signed-off-by: Laszlo Ersek <lersek at redhat.com> --- generator/C.ml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/generator/C.ml b/generator/C.ml index f9171996dde0..07c924c48ccf 100644 --- a/generator/C.ml +++ b/generator/C.ml @@ -250,15 +250,15 @@ let *)

...ough. >> > > Agree. These 3 will help emit-one-CU-at-a-time. I was thinking if we are > going to enforce the single assumption, it may be easier to enforce 3 > general assumptions which can make emit-one-CU-at-a-time easier. > I'm just going to ignore the cu-at-a-time work/subthread for now, it may be best to discuss that separately, unless you want to decide on a design for the cross-CU-dies that is forward-looking enough to simplify cu-at-a-time (ie: by never mutating a prior CU after it has been constructed) but I don't think that would be helpful. - David ------------...