search for: unconcern

...s. Anyway: If we have a 128kbs signal coming down a *udp* channel with close to 25% packet loss, it would be really nice if it sounded like a 96kbs signal, not a choppy 128kbs. Short question: is this possible and feasible? Extended question/scenario: It is of course easy to achieve if we are unconcerned about the absolute quality. Just define a 128kbs stream to be a 2-redundant 64kbs stream, and voila, we have graceful degradation. That's none to nice tho. That's still an all-or-nothing affair. Instead, we'd like to have the property of the codec that it be possible to separate th...

...Priority: P2 Component: sftp AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: spin at avalon.net The man page states that sftp -b will abort when commands (including get) fail. However, when I give sftp a list of get -P commands via the -b option it continues unconcerned when the requested file doesn't exist and it doesn't exit with a error code either (which would be enough for me.) # /usr/bin/sftp -b /tmp/files roger at remote && echo ok Connecting to remote... sftp> GET -P /data/200211/njxj1-cdr_2002_11_30__11_00_00.cdr Couldn't stat re...

We have an LDAP server that contains AES encrypted passwords. So far I've been able to use this by adding a passdb module that encrypts the user's password prior to ldap comparison. Now I am looking at supporting client-side encrypted passwords. To do this I need to decrypt the password returned by LDAP. Is there a way to insert a module to do this decryption between ldap returning and

CentOS is simply great. I use it as my main desktop. I use VMWare clients for any "special needs" software. I am struggling a bit with the plethora of repos and looking for some advice. Would you opine with detail on the best repo setup for a desktop CentOS 5? Comments: rpmforge provides fine rpms. kbsingh, google, adobe, kde-redhat, CentOS-Testing , CentOS-fastrack, epel,

...y (Nottingham) who are R supportive but have no cgi-bin expertise so I'm asking more widely now. Our/my history is of getting good papers out and we have good ones on uses of the system in submission and in press as well as as a sample list below. Unless I do most of the work I'm very unconcerned about where my name comes in co-authorship as I'm not under RAE pressures, just my own and NHS pressures to move this initiative on. Hence it may be a good link up for people. I currently have legitimate access to anonymised datasets from a few thosand in specific (multi-practitioner)...

...ertaining to the MSYS2 and/or MinGW environments, and a swig compiled for use by xapian-bindings? The dlopen issue I believe is POSIX and therefore not relevant to a mingw-w64-i686 (or mingw-w64-x86_64) environment; and furthermore -lieee returns 'yes' on GNU/Linux. I should say that I am unconcerned whether potential responses pertain to 1.4.1 stable or to 1.2.x old stable series. Eric at Erics-Netbook MINGW32 ~ $ cd /c/WORK/swig-3.0.7 Eric at Erics-Netbook MINGW32 /c/WORK/swig-3.0.7 $ export PATH=/mingw32/bin:/usr/local/bin:/usr/bin:/bin:\ > /c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/Sy...

...s compatible, allowing MTE-globals built binaries to run on old ARM64 hardware (as no incompatible instructions are emitted), the same as heap tagging. Stack tagging requires a new ABI - and we expect the MTE globals scheme to be enabled in partnership with stack tagging, thus we are unconcerned about the ABI requirement for the MTEGLOBTAG scheme. Please let us know any feedback you have. We're currently working on an experimental version and will update with any more details as they arise. Thanks, Mitch. -------------- next part -------------- An HTML attachment was scrubbed......

...patible, allowing MTE-globals built binaries to run on old ARM64 > hardware (as no incompatible instructions are emitted), the same as heap > tagging. Stack tagging requires a new ABI - and we expect the MTE globals > scheme to be enabled in partnership with stack tagging, thus we are > unconcerned about the ABI requirement for the MTEGLOBTAG scheme. > > > > > > Please let us know any feedback you have. We're currently working on an > experimental version and will update with any more details as they arise. > > > > > > Thanks, > > > > M...

...eme is backwards compatible, allowing MTE-globals built binaries to run on old ARM64 hardware (as no incompatible instructions are emitted), the same as heap tagging. Stack tagging requires a new ABI - and we expect the MTE globals scheme to be enabled in partnership with stack tagging, thus we are unconcerned about the ABI requirement for the MTEGLOBTAG scheme. >>> > >>> > >>> > Please let us know any feedback you have. We're currently working on an experimental version and will update with any more details as they arise. >>> > >>> > >...

alan said: > I think I am in agreement, > if by "isn't necessary" you mean to say that > simply providing more features to Markdown > doesn't force end users to use them, > or even really know they exist. except that wasn't what i meant. i mean that it's not necessary to trade simplicity in order to get the power of additional

> On Dec 23, 2014, at 1:40 PM, Chandler Carruth <chandlerc at google.com> wrote: > > If we're going to talk about what the right long-term design is, let me put out a different opinion. I used to be somewhat torn on this issue, but this discussion and looking at the particular intrinsics in question, I'm rapidly being persuaded. > > We shouldn't have any target

Hi all, Currently I'm looking for users of the --keep-foreign-metadata feature of FLAC. There has been some improvement of this feature in FLAC 1.4.0. Since 2007 there has been a warning in FLAC that --keep-foreign-metadata is a new feature. I think removal of this warning is long overdue, but there are still some issues surrounding it. So, if there are users of this feature on the mailing

...es to run on old ARM64 > > hardware (as no incompatible instructions are emitted), the same as > heap > > tagging. Stack tagging requires a new ABI - and we expect the MTE > globals > > scheme to be enabled in partnership with stack tagging, thus we are > > unconcerned about the ABI requirement for the MTEGLOBTAG scheme. > > if object access goes via symbolic dynamic relocation > (GOT, ABS) then there is no need to do anything special: > > - pointer representation is controlled by the dynamic > linker via the relocs > > - location of o...

We've pretty happy now with a patch that adds two wrappers around SmallVector that make it 1) more convenient to use and 2) will tend to mitigate misuse of SmallVector. We think it's ready for wider discussion: https://reviews.llvm.org/D90884 SVec<T> is a convenience alias for SmallVector<T, N> with N chosen automatically to keep its size under 64 Bytes (that heuristic is easy