search for: muddies

On Fri, Nov 13, 2015 at 9:25 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote: > Hello Hans, > > Not to muddy the waters or anything, have you thought about the NIR > integration that Rob was thinking about ? > I'm pretty sure he'll be happy to have extra people helping him out. How would that in any way plug into llvm or nouveau? There's no OpenCL C ->

Hi Jean-Marc, You make that sound like its just a matter of meeting some arbitrary spec. Let's be more specific..... If you use narrow band voice down to deep bass frequencies: - 16 bit linear audio sounds good - alaw or ulaw sounds muddy - low bit rate codecs, like speex or G.729, sound awful. I assume QinBin only listened to some uncompressed audio in his evaluation.

Hi Robin, On 15 August 2014 21:49, Robin Morisset <morisset at google.com> wrote: > I have > attached the corresponding patches; they are not completely ready for review > (mostly missing tests), I would just like to make sure that the general > approach seems reasonable. I've had a quick glance at the patches, and the code seems fairly sane. But I'm not so sure about

David Blaikie <dblaikie at gmail.com> writes: > Selfhost clang. Whenever we get a warning from Clang we either fix > Clang or fix the build quite quickly. Not possible, > If you want to fix the build such that LLVM can be built -Werror clean > with GCC the right solution is going to be to turn off -Wuninitialized > when the LLVM build system detects that it is using GCC

The distinction between the LLVMTargetMachine and TargetMachine classes has become somewhat muddy recently. So I created: https://reviews.llvm.org/D38482 to clean things up. During review it was noted that we may rather merge the two instead which looks like this: https://reviews.llvm.org/D38489 <https://reviews.llvm.org/D38489> We really should choose one of the two over the status quo.

Feb 27 14:17:46 wurfel dovecot: imap-login: Login: user=<USER>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 27 14:17:46 wurfel dovecot: IMAP(USER): file mbox-sync-update.c: line 387 (mbox_sync_update_header): assertion failed: (ctx->mail.uid != 0 || ctx->pseudo) This is happening for dozens of users. Anyone have a suggestion of what to adjust? It was happening somewhat

Hello, I'm having a bit of a problem with a plot, and I'm hoping that someone might be able to help. I'm running the R Cocoa Gui v1.12 on OS X 10.4.2, and I'm doing a stacked bar plot. The plot itself is quite simple: barplot(as.matrix(s.strats.in),main="Strategy when strong", col=strat.col) where s.strats.in is a matrix with a number of rows that define the height

Crew, I've run into something a little odd with the vorbis encoder and would like some input. I use SpacialAudio's SAM3 Broadcaster and am having problems with the ogg encoder when I create a mono output stream. It seems as if the signal level of the left and right sides are being combined before the encoding process, leaving the sound muddy and overdriven. As such, if I reduce

On Wed, Nov 30, 2011 at 10:42 PM, Chris Lattner <clattner at apple.com> wrote: > On Nov 29, 2011, at 12:26 AM, David Blaikie wrote: >> For a bit of an experiment I've been trying to compile LLVM & Clang >> with -Weverything (disabling any errors that seem like more noise/less >> interesting). One warning I've recently hit a few instances of is >>

On Aug 19, 2009, at 11:19 PM, Erick Tryzelaar wrote: > On Wed, Aug 19, 2009 at 11:08 PM, Chris Lattner<clattner at apple.com> > wrote: >> >> As we discussed on IRC, I don't think there is any reason for the >> implementation of these methods to check these invariants. These >> are clear >> API invariants that the caller can check if needbe.

Hi people! I've been hunting around the web for an answer to this question for a couple of days now. I run the IT for a small company and i don't have a lot of experience with the type of C-ISAM database application that is used by my company, I deal with the general IT issues and call in specialists when required. But I need to backup this 10GB database to a disaster recovery

David Blaikie <dblaikie at gmail.com> writes: >>> Selfhost clang. Whenever we get a warning from Clang we either fix >>> Clang or fix the build quite quickly. >> >> Not possible, > > Out of curiosity - why not? (sure, I realize everyone has internal > build systems, etc, that they're ultimately integrating LLVM into - > but that doesn't mean

On Thu, Jan 3, 2013 at 11:16 AM, <dag at cray.com> wrote: > David Blaikie <dblaikie at gmail.com> writes: > >> Selfhost clang. Whenever we get a warning from Clang we either fix >> Clang or fix the build quite quickly. > > Not possible, Out of curiosity - why not? (sure, I realize everyone has internal build systems, etc, that they're ultimately

On Thu, Jan 3, 2013 at 10:52 AM, <dag at cray.com> wrote: > David Blaikie <dblaikie at gmail.com> writes: > >> The other point Chandler was making, though, was that this sort of fix >> means that other tools (Valgrind/MemSan) won't catch a broader class >> of errors because we will have silenced them too. > > Does buildbot do a valgrind build with the

On Wed, Aug 19, 2009 at 11:08 PM, Chris Lattner<clattner at apple.com> wrote: > > As we discussed on IRC, I don't think there is any reason for the > implementation of these methods to check these invariants.  These are clear > API invariants that the caller can check if needbe.  Making the > implementation check these will slow down clients which are known to be well >

I''m trying to set puppet up to manage users and groups on an OpenBSD Samba server, but puppet doesn''t want to handle group names with spaces. I know this horribly ugly, but compatibility with windows clients seems to demand groups like "Domain Users" and "Domain Computers", and puppet chokes on them even though the underlying OS handles them at least well

On 7/6/20 11:00 AM, Rowland penny via samba wrote: > On 06/07/2020 16:29, Georg.Biberger--- via samba wrote: >> Hello, >> >> Get same output with "getent passwd qqeda11" and with "cat /etc/passwd | grep >> 'qqeda11'" >> qqeda11:x:79846:65600:Project Account for EDA:/home/qqeda11:/bin/bash >> When you say it is not supported, do

On Tue, Oct 3, 2017 at 8:54 AM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On 10/02/2017 10:57 PM, Matthias Braun via llvm-dev wrote: > > The distinction between the LLVMTargetMachine and TargetMachine classes > has become somewhat muddy recently. So I created: > > https://reviews.llvm.org/D38482 > > to clean things up. During review it was

I have a few questions to throw out to the collective braintrust. 1. in core/fs/pxe/tftp.c, when communicating using udp, in connecting, transmitting and receiving functions, errors are not communicated to the user. In fact the comment after transmit specifies "/* If the WRITE call fails, we let the timeout take care of it... */" The question is: Should we notify the user that there

On Fri, Dec 07, 2018 at 04:48:41PM +0800, Tiwei Bie wrote: > Introduce VIRTIO_RING_NO_LEGACY to support disabling legacy > macros and layout definitions. > > Suggested-by: Michael S. Tsirkin <mst at redhat.com> > Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> > --- > VRING_AVAIL_ALIGN_SIZE, VRING_USED_ALIGN_SIZE and VRING_DESC_ALIGN_SIZE > are not pre-virtio