search for: muddy

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 -> NIR, and there's no NIR -&g...

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. Steve On 03/03/2010 07:39 PM, Jean-Marc Valin wrote: > The notch filter is specifically designed to cut below 200 Hz when > working in narrowband. In wi...

...w > (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 starting with a new pass then deleting the other two. I think it's likely to muddy the revision control history. I'd prefer to see a gradual evolution of the AtomicExpandLoadLinked.cpp (perhaps starting with a "git mv" and some internal renaming to stake out the intent, followed by adding and using the extra hooks). Cheers. Tim.

...s that it is using GCC rather than > Clang (we have the inverse, where we turn on certain Clang warning > flags when we detect that we're using Clang). I would like to keep -Wuninitialized if at all possible because it does in fact detect bugs. > Pragmas: maybe, but it would probably muddy the waters a fair bit. > Depends how noisy any given warning is - I suspect -Wuninitialized > wouldn't meet the bar for pragma suppressions (there would be too many > suppressions) & should just be disabled in the build system when using > GCC. We can rely on Clang's warning...

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 q...

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

...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 the output level by 6db, the combined streams are at the right level. The settings I'm using are Quality -1, 32kbps/44kHz. SpacialAudio suggested that they are passing the audio info to the library as required. Ideas? -I

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 >>

...it's the client's responsibility to make sure that the string > isn't invalid. Which then follows that the assertions checking the > validity of the string should stay. You're right that anything can be declared to be a property the caller needs to enforce. This makes it a muddy issue that boils down to a judgement call based on how low-level the API is and how complex the invariant is. Two examples: Since APInt is a very low level class, bitwidth is something clients can be expected to have to know about. Since detecting errors in floating point string literals b...

...the general IT issues and call in specialists when required. But I need to backup this 10GB database to a disaster recovery server on the other side of the continent. So my first reaction was that if the database was shutdown then rsync would be a great solution! But some opinions on the net muddy the issue. Tridge's PHD thesis mentions that people use rsync for replicating their databases to backup servers. i would have thought that that was OK if the DBM was shutdown during the backup...... But some people on the net like this: http://www.sanitarium.net/golug/rsync_backups.html S...

...se gcc to build our whole compiler and we develop, test and release all using the same build process so that things are consistent. In the past we've been burned when developers use a different process and don't see bugs that testers see. >>> Pragmas: maybe, but it would probably muddy the waters a fair bit. >>> Depends how noisy any given warning is - I suspect -Wuninitialized >>> wouldn't meet the bar for pragma suppressions (there would be too many >>> suppressions) & should just be disabled in the build system when using >>> GCC. We...

...39;re using Clang). > > I would like to keep -Wuninitialized if at all possible because it does > in fact detect bugs. I'm not saying it doesn't detect bugs. My statement(s) were made with that (& other issues mentioned) in mind. >> Pragmas: maybe, but it would probably muddy the waters a fair bit. >> Depends how noisy any given warning is - I suspect -Wuninitialized >> wouldn't meet the bar for pragma suppressions (there would be too many >> suppressions) & should just be disabled in the build system when using >> GCC. We can rely on Cla...

...de runs to > check for the garbage value? Then even non-valgrind builds will catch > the problem. Complicates the code & isn't necessarily trivial/obvious in complex cases (& there isn't always a convenient garbage value to use either). Pragmas: maybe, but it would probably muddy the waters a fair bit. Depends how noisy any given warning is - I suspect -Wuninitialized wouldn't meet the bar for pragma suppressions (there would be too many suppressions) & should just be disabled in the build system when using GCC. We can rely on Clang's warnings to catch things th...

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

...> > The LOCAL Unix user != the Domain user > IMHO, these discussion are beneficial. "compat" traces back to NIS (mostly), so usually means a "combo" search of "+/-" style NIS or other allow/deny sources in addition to /etc/passwd (group, etc.). This may muddy the waters a bit, but this what I wrote in our ansible module that creates users. # # IMPORTANT: There are namespaces in Linux (as in most Unix). Therefore, # it is possible for there to be a local Linux account defined in # /etc/passwd, /etc/shadow, etc. and a like named account coming in from #...

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 noted that we may rather merge > the two instead which looks like this: > > https://reviews.llvm.org/D38489 > > We really should choose one of the two over the status...

...on failed and the transmit never hit the wire. Of course, the receive also failed. If anyone would like to see the changes we made to use pxebc, I would be happy to post but thought there is probably a very good reason in other environments to recreate the udp connections and didn't want to muddy the waters. I also think it may not be a complete solution. Gene, I just pulled down the latest commit and will try it in both my standalone environment (subnet 1 dhcp server, subnet 2 client, proxy and tftp server) as well as my customer's environment, mentioned above. I'll post the r...

...idea. If we want this, we may also want > to define _SPLIT_ version for them. I don't think it's a good idea to have alignment in there - the point of NO_LEGACY is to help catch bugs not to sanitize coding style IMHO. And spec calls "legacy" the 0.X interfaces, let's not muddy the waters. > > include/uapi/linux/virtio_ring.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/include/uapi/linux/virtio_ring.h b/include/uapi/linux/virtio_ring.h > index 9b0c0d92ab62..192573827850 100644 > --- a/include/uapi/linux/virtio_ring.h > +++ b/in...