similar to: libvorbis and floating point exception

Hello, I'm not quite sure if this is the right list for my questions, please excuse if it isn't. 1. While using vorbislib (Win2K/Borland C++ Builder 5), I'm getting reproducible floating point exceptions at lots of sample rate/bit rate combinations. For example, the original encoder_example.c, with just the initialization line changed to

Hi So far when I have streamed Vorbis, the headers (the 3 first frames/packets) was not included in the stream, but communicated out of band typically in an SDP file as unparsed A-lines. Rethinking that concept, I'm wondering if it is really necessary to do it that way. Isn't it possible in a platform independent way to regenerate useable headers on the client side using just the

Hi all, I've been hitting the odd floating point exception errors using the new alpha encoders. They're encoding a live stream so I can't reproduce the crash on demand, and it might only happen once every few days so it's been fun trying to get a backtrace. The crash happens in a fairly scary block of code, I wouldn't have a clue where to begin trying to fix it!

I've been working on tracking down a variety of problems with the post beta2 branch, mostly related to floating point precision issues, which cause floating point exceptions. These tend to have nasty effects like making libvorbis not work on your typical alpha (which doesn't mask them like x86 does by default). These seem to be turning up in a number of places, mainly in psy.c - I'm

Hi I'm trying push for companies and government institutions to start using Vorbis as an alternative to MP3 and to some extend AAC so they as a benefit can ignore rigid license schemes and expensive royalty payments. In principle it ought to be a downhill job, but it has turned out to be a lot more difficult than expected. The biggest obstacle for government institutions and to some extend

Hi I read in http://grahammitchell.net/writings/vorbis_intro.html > Ogg Vorbis files support "bitrate peeling", which means you can produce > a lower bitrate file from a higher bitrate file without re-encoding and > at the same quality as if you'd encoded the file directly into the lower > bitrate from the original file. No other lossy audio codec currently > supports

Hey guys, I just released my new MacOSX-based OpenAL implementation...part of it is a Ogg Vorbis decoder based on the 1.0 reference libraries. I spent some time optimizing them and found that many of the hotspots in libvorbis are perfect candidates for vectorization, so I wrote Altivec versions of them. The end result? Decoding of a .ogg file is between 30 and 50% faster on a Mac with an

I received a floating point exception from "make check" on a Linux alpha (Red Hat 6.0) using egcs-1.1.2 compiler, and compiling from R-base-0.64.1-5.src.rpm packaged by Red Hat Contrib|Net. make check fails with return code 136 from modreg-Ex.Rout. The final output is: > plot(update(rock.ppr, sm.method="gcv", gcvpen=2), + main = "update(...,

Hi, I got "Floating point exception" when running linux/syslinux using syslinux 3.72. How to reproduce: 1. On debian Etch, kernel 2.6.24-etchnhalf.1-686 2. wget http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.72.tar.bz2 3. tar xvjf syslinux-3.72.tar.bz2 4. syslinux-3.72/linux/syslinux --help 5. An error message "Floating point exception" was shown. Same problem

On Wed, 19 Apr 2006 19:28:34 +0100 Simon Burton <simon at arrowtheory.com> wrote: > > >From what I remember, this is a bug in debian libc: > some floating point flags are set incorrectly causing SIGFPE. > Can't find the bug report ATM. Oh, it just showed up on numpy-discussion: http://sources.redhat.com/bugzilla/show_bug.cgi?id=10 """ #include

On Thu, 20 Apr 2006, Simon Burton wrote: >>> From what I remember, this is a bug in debian libc: >> some floating point flags are set incorrectly causing SIGFPE. >> Can't find the bug report ATM. > > Oh, it just showed up on numpy-discussion: > http://sources.redhat.com/bugzilla/show_bug.cgi?id=10 > > """ > #include <fenv.h> > void

On Wed, Mar 18, 2009 at 2:22 PM, Jason Riedy <jason at acm.org> wrote: > Does anyone have suggestions for either extending operators or > adding intrinsics that support multiple return values? Intrinsics already support multiple return values. See int_sadd_with_overflow and friends. >  Or is > packaging everything into a derived types the only way? > There's already

Does anyone have suggestions for either extending operators or adding intrinsics that support multiple return values? Or is packaging everything into a derived types the only way? I have an idea for supporting floating-point exception flags and modes in a flexible way by making the data dependencies explicit, but I've become quite lost poking around. I suspect this will end up involving

I'm getting a floating point exception from ssh on an opteron running Linux (in 64 bit). It happens only when I ssh out to a server not supporting SSHv2 and when its public key is not already in the key file. Right after I answer "yes" to the "Are you sure?" prompt I get the exception. Here is the stack trace: Program received signal SIGFPE, Arithmetic exception

alpha 21164 (EV56) debian unstable debian's vorbis 1.0 beatles yellow submarine track 9, "sea of holes" 96% of the way through i get a floating point exception. reproduced twice in a row. if a developer does not have a copy of this fine album, i can upload the wav file. ~jeffrey :j --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

> x <- matrix(1:10, ncol = 2) > xc <- cor(x[, 2], x[, 0]) > cbind(xc, vector()) Process R floating point exception at Tue Feb 11 19:16:51 2003 > version _ platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 6.2 year

Hello everyone, I am co-hosting a BoF at next week's LLVM Dev Meeting to discuss enhancements to floating point support that will enable non-default rounding and FP exception modes. I've just uploaded a set of slides that provides details about the topics I hope to cover. You can find it here (look for the link just below the speaker profiles): http://sched.co/8Yzr I hope the BoF will

Hi Simon, The x86 backend does generate scalar SSE2 instructions. For your example, it should emit something like: .text .align 4 .globl _sum_d _sum_d: subl $12, %esp movl 20(%esp), %eax movl 16(%esp), %ecx cmpl $0, %eax jne LBB_sum_d_2 # cond_true.preheader LBB_sum_d_1: # entry.bb9_crit_edge pxor %xmm0,

On Tue, 18 Apr 2006 23:27:39 -0700 Evan Cheng <evan.cheng at apple.com> wrote: > Hi Simon, > > The x86 backend does generate scalar SSE2 instructions. For your > example, it should emit something like: Oh, how did you get this ? [...] > > There is nothing here that should cause an exception. Are you using a > release or cvs? CVS. >From what I remember,

I'm please to announce the release of libvorbis 1.3.5. libvorbis is the reference encoder and decoder implementation for Ogg Vorbis files. This is a maintenence release which fixes some issues and updates the build. Upgrading is recommended for all users. Source is available from: * http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.xz *