Re: WORKAROUND: transcode-1.0.0-1.2.fc4.i386.rpm - segmentation fault
"Gerald B. Cox" <[email protected]>
| Newsgroups | gmane.linux.freshrpms.user |
|---|---|
| Message-ID | <20050808072730.y0bm8xf5s0sg448w@charon> |
Ralf: Below is the output from /proc/cpuinfo. I do see "sse" listed, but not "sse2". I just know that when using either "sse" or "sse2" transcode doesn't work for me. I also find it weird that the "autodetect" option of "--accel" appears to work. I thought "autodetect" was the default option. I now wonder if the default is "SSE" and if the implementation in transcode is Intel specific (seems unlikely, but that is the way it appears, cause it doesn't work - and apparently folks with Intel or AMD 64 processors aren't reporting this problem). Am VERY curious as to what is going on... Thanks! processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 3200+ stepping : 0 cpu MHz : 2191.117 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 4341.76 Quoting Ralf Ertzinger <[email protected]>: > Hi. > > "Gerald B. Cox" <[email protected]> wrote: > >> I have AMD Athlon XP 3200+. > > That one should do SSE2. Look at /proc/cpuinfo. > >> experimenting with the --accel option. If I use "--accel autodetect" >> it also works. If I use SSE or SSE2 as an option, transcode fails with >> a "segmentation fault". > > When I find the time I'll look at it. If I do not forget about > this before :) > > -- > Funeral in the morning, IDE hacking in the afternoon and evening. > -- Alan Cox, Diary December 3 2002 >