search for: subthread

Displaying 20 results from an estimated 65 matches for "subthread".

2007 Apr 20
1
Voicemail to Text Transcription(was: Re: [asterisk-dev] Voicemailto text translation)
(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...
2025 Jan 24
1
Opus 1.5.2 low hum in input file results overblown output at decoding
There was a post in the Opus subthread on HA where there was a link to the file called Opus-tools-0.2-34-g98f3ddc_(using_libopus_1.5.2-21-gff6dea5)_Win_GCC142.7z. That's the one I'm currently using. First, I used GoldWave to convert your input file from ?-law to PCM and saved it as a ".wav" file. Next, I encoded it w...
2020 Apr 04
0
[PATCH 5/6] kernel: better document the use_mm/unuse_mm API contract
...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...
2020 Apr 16
0
[PATCH 2/3] kernel: better document the use_mm/unuse_mm API contract
...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...
2015 May 15
2
[LLVMdev] RFC: ThinLTO Impementation Plan
...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>
2019 Oct 02
4
[RFC] Propeller: A frame work for Post Link Optimizations
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...
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
...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...
2015 May 15
3
[LLVMdev] RFC: ThinLTO Impementation Plan
...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. > >...
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
...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] > > ... > >...
2014 Dec 02
2
[LLVMdev] TBAA vs !invariant.load metadata semantics
> 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...
2014 May 16
0
Bug#748052: Bug#748052: Info received (Bug#748052: Info received ( B
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
2020 Jul 06
0
[PATCH 18/18] arm64: lto: Strengthen READ_ONCE() to acquire when CLANG_LTO=y
...; 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
2007 Apr 04
0
Voicemail to Text Transcription(was: Re: [asterisk-dev] Voicemail to text translation)
(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...
2025 Jan 28
1
Opus 1.5.2 low hum in input file results overblown output at decoding
...us-bounces at xiph.org> On Behalf Of Petr Par?zek Sent: Friday, January 24, 2025 12:03 PM To: opus at xiph.org Subject: Re: [opus] Opus 1.5.2 low hum in input file results overblown output at decoding ?EXTERNAL EMAIL - Please use caution with links and attachments? There was a post in the Opus subthread on HA where there was a link to the file called Opus-tools-0.2-34-g98f3ddc_(using_libopus_1.5.2-21-gff6dea5)_Win_GCC142.7z. That's the one I'm currently using. First, I used GoldWave to convert your input file from ?-law to PCM and saved it as a ".wav" file. Next, I encoded it wit...
2019 Oct 07
2
[RFC] Propeller: A frame work for Post Link Optimizations
...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...
2016 Nov 17
2
RFC: Consider changing the semantics of 'fast' flag implying all fast-math-flags
...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 >>>>> >>...
2020 Apr 04
14
improve use_mm / unuse_mm
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.
2020 Apr 04
14
improve use_mm / unuse_mm
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.
2015 Mar 20
0
[PATCH 1/1] Add virtio-input driver.
...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...
2015 Mar 20
0
[PATCH 1/1] Add virtio-input driver.
...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...