similar to: apsort

Hi, I am submitting a small patch for Vorbis psy.c... * Make use of NEGINF constant where possible Does this look OK? - Michael Index: psy.c =================================================================== --- psy.c (revision 18737) +++ psy.c (working copy) @@ -29,7 +29,7 @@ #include "scales.h" #include "misc.h" -#define NEGINF -9999.f +#define NEGINF (-9999.f)

Solaris 5.8 has a quirky qsort that requires the ability to recognize elements as equal. here is a patch I have created to deal w/ this problem. I apologize if the patch is in the wrong format and would love to be corrected if wrong. I used the following to create the patch libvorbis-1.0> diff -u lib/psy.c lib/psy_new.c > libv.patch <p><p><p><p> --------------

I have found a bug in libvorbis-1.0. I have found a fix, but need to know in what format and to where to sumbit the patch. It involves a quirky qsort in Solaris 5.8 that dumps core without the patch. The fix involves editing vorbis/lib/psy.c <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

On Tue, Apr 15, 2014 at 12:33 PM, Peter Meerwald <pmeerw at pmeerw.net> wrote: > Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net> > --- > libspeexdsp/resample.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/libspeexdsp/resample.c b/libspeexdsp/resample.c > index e32ca45..a19b997 100644 > ---

Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net> --- libspeexdsp/resample.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/libspeexdsp/resample.c b/libspeexdsp/resample.c index e32ca45..a19b997 100644 --- a/libspeexdsp/resample.c +++ b/libspeexdsp/resample.c @@ -85,7 +85,7 @@ static void speex_free (void *ptr) {free(ptr);} #ifdef FIXED_POINT #define

Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/nvc0/nvc0_context.h | 7 +- src/gallium/drivers/nouveau/nvc0/nvc0_program.c | 2 +- src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 20 ++-- src/gallium/drivers/nouveau/nvc0/nvc0_screen.h | 3 + src/gallium/drivers/nouveau/nvc0/nvc0_state.c | 27 +++--

Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/nvc0/nvc0_context.h | 7 +- src/gallium/drivers/nouveau/nvc0/nvc0_program.c | 2 +- src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 20 ++-- src/gallium/drivers/nouveau/nvc0/nvc0_screen.h | 3 + src/gallium/drivers/nouveau/nvc0/nvc0_state.c | 27 ++++-

On Tue, Aug 13, 2013 at 5:58 AM, Kuperstein, Michael M < michael.m.kuperstein at intel.com> wrote: > Hi,**** > > ** ** > > It looks like SimplifyLibCalls has a tendency to emit calls to libm > functions without checking with TLI whether these calls are available.**** > > For example, PowOpt has this code:**** > > ** ** > > struct PowOpt : public

Hi, It looks like SimplifyLibCalls has a tendency to emit calls to libm functions without checking with TLI whether these calls are available. For example, PowOpt has this code: struct PowOpt : public UnsafeFPLibCallOptimization { PowOpt(bool UnsafeFPShrink) : UnsafeFPLibCallOptimization(UnsafeFPShrink) {} virtual Value *callOptimizer(Function *Callee, CallInst *CI, IRBuilder<> &B)

+Tanya for the account issue. > On Oct 27, 2016, at 11:36 AM, Eric Martin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. > > I've written 2 test functions in C that take in a float array x of size n and output

Hi, I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized:

Eric, I apologize for any delay or confusion. From my records/list archives, I saw that Anton had created an account for you on Oct 17th and responded to your email to llvm-admin. I am not sure what happened after that point as I thought the account was done. I just confirmed there is an account for you in bugzilla, so you should be good to go if you reset your password. -Tanya > On Oct 27,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <p>Hello, I have encountered a situation where oggenc core dumps. I am using vorbis-tools 1.0 on Solaris 8 x86. This is the command line: oggenc -b 128 -a "Keith, Toby" -t "Losing My Touch" -l "Unleashed" \ - -N "06" -o "Keith, Toby - 06. Losing My Touch.ogg" audio_06.wav Here is a

I am trying to add the bigmemory packages but I get the following error message: In file included from bigmemory.cpp:14:0: ../inst/include/bigmemory/isna.hpp: In function 'bool neginf(double)': ../inst/include/bigmemory/isna.hpp:22:57: error: 'isinf' was not declared in this scope make: *** [bigmemory.o] Error 1 ERROR: compilation failed for package 'bigmemory' * removing

Hello, some misc. cleanup patches for speexdsp, nothing big I'm not sure about how to submit patches, so this is a test balloon :) ultimately, I'd like to fix the FIXED_POINT issue, see http://lists.xiph.org/pipermail/speex-dev/2013-December/008465.html currently, I think the only way to find out how speexdsp has been compiled is to resample some bytes and observe the output; which is

Hi lists, Sorry for cross-posting, but these two patches are of concern to clang and llvm. I'm compiling C-code which includes inline assembler which looks like the following using the sparc-target: static inline float fabsf(float a) { float res; __asm __volatile__("fabss %1, %0;" : "=f"(res) : "f"(a)); return

Hi Patrick, I do not see a problem with those patches --- apart from missing tests ;) Cheers, Arnaud On Mon, Mar 21, 2016 at 3:11 PM, Patrick Boettcher via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hi lists, > > Sorry for cross-posting, but these two patches are of concern to clang > and llvm. > > I'm compiling C-code which includes inline assembler which looks

Commit ad4dc772 fixed an issue with the viewport not being restored correctly. However it's rather hackish and confusing. Instead just mark the viewport dirty and let the viewport validation take care of it. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nvc0/nvc0_context.h | 1 - src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c | 5

xclock is the classic X Window System clock utility. It displays the time in analog or digital form, continuously updated at a frequency which may be specified by the user. Alan Coopersmith (3): Use _CONST_X_STRING to make libXt declare String as const char * Clear -Wsign-compare warning from gcc 7.3 xclock 1.0.9 Jon Turney (1): Consistently use X_GETTIMEOFDAY Niclas

Your change looks almost correct. You need: - Test cases. - Add the new 'f' type to the documentation in LangRef.rst. - Check the type of the arg (f32, f64, or f128) to choose the right one of FPRegsRegClass, DFPRegsRegClass, QFPRegsRegClass. Then, please submit for review, per http://llvm.org/docs/DeveloperPolicy.html (Typically best to do so via Phabricator,