similar to: vorbisenc creates silent ogg files on ARM EABI

Hi, Paul Curtis wrote: > If you read the Arm Architecture document for ARMv5, it states for MUL: > > "Operand restriction: Specifying the same register for <Rd> and <Rm> was > previously described as producing UNPREDICTABLE results. There is no > restriction in ARMv6, and it is believed all relevant ARMv4 and ARMv5 > implementations do not require this

Hi, A short mail to let you know that the MSVC project files aren't OK compared to the Makefiles. Indeed they include the vorbisenc part (vorbisenc.c file, and vorbis_encode_* function names in the .def file) inside the vorbis library, and they also point to a non-existant file (bitbuffer.h) Here is a patch to fix this, in case you are interested (patch made on the win32 directory using

Hey oddsock, I was wondering why vorbisenc.dll is statically linked inside oddcastv3, yet vorbis.dll, ogg.dll, etc is not. This means I cannot update my stream to use a newer version of the encoder, and I can't try other tunings of encoders. I'm wondering if this is a mistake since vorbisenc.dll is distributed in your package, yet it is not used. It would be very nice if you could

Hello, When I compile either oggenc or encoder_example with static libraries, they work fine, but when I try them with the dynamic libraries, I get an access violation in vorbisenc.dll with both oggenc and encoder_example. Can anyone on win32 confirm this? It's strange because vorbisfile.dll *does* work with vorbisfile_example, and the configuration for vorbisfile.dll is exactly the same

Hi, I'm trying repeatedly to get some more information on the vorbis encoding API. My last questions on this list were regarding vorbis_encode_ctl(). Of course prior to posting such questions to the list, I checked the vorbis web site for info. Unfortunately there is no information on the related function, the page http://www.xiph.org/ogg/vorbis/doc/vorbisenc/vorbis_encode_ctl.html

On Thu, Oct 13, 2011 at 11:25 AM, Joe Abbey <jabbey at arxan.com> wrote: > LLVM Supports: > ARMv4T  -> ARM7TDMI > ARMv5TE -> ARM926EJ-S >         -> XScale > ARMv6   -> ARM1136J(F)-S > ARMv6ZK -> ARM1176JZ(F)-S > ARMv7A  -> Cortex-A8 >            Cortex-A9 > ARMv7M  -> Cortex-M3 Does the LLVM code generator generate Thumb code in addition to

Hi, I released a BladeEnc-style wrapper for the Ogg Vorbis 1.0 codec which works with my CD ripper ACXtractor. You can download it from http://www.marvintec.com/en_download.htm Many thanks for all this great work ;-) <p>Best regards Stefan Schulz/ MarvinTec mailto:support@marvintec.com http://www.marvintec.com http://www.marvintec.de <p>--- >8 ---- List archives:

2008/12/28 Keun Soo Yim <yim6 at illinois.edu> > This is a simple question about building ARM cross-compiler. > What is the building procedure using LLVM 2.4 and GCC front-end 4.2? > > I used these commands for LLVM, and it is okay. > > $ ../configure --prefix=/usr/local -target=arm > $ make ENABLE_OPTIMIZED=0 > $ make ENABLE_OPTIMIZED=0 install > > Then

Just got around to compiling RC3 under beos and came across an anomaly when using managed bitrates. I haven't changed the code for the beos encoder but I now get double the bitrates so vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); now gives me vorbis files that average around 325 - 350. Is this now the correct

I was trying to using llvm to targeting ARMv5TE -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180314/b9dadc37/attachment.html>

Hi,     I am able to crosscompile llvm-gcc using --with-arch=armv6 but cannot using --with-arch=armv5. Can anyone please tell me what option i should use to crosscIompile for the architecture armv5te (xscale processor). I heard that by default arm 5 code generates, will that work on my target (armv5te)? I get the following when I use --with-arch=armv5 :    

On Wed, Jul 18, 2012 at 6:08 PM, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > On Wed, Jul 18, 2012 at 5:45 PM, Renato Golin <rengolin at systemcall.org> wrote: >> On 18 July 2012 15:46, salvatore benedetto >> <salvatore.benedetto at gmail.com> wrote: >>> $ clang++ -ccc-host-triple thumbv7m-none-gnueabi noInclude.cpp -c >>>

Well how about as a strawman... taking some options from http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores and http://en.wikipedia.org/wiki/List_of_applications_of_ARM_cores LLVM Supports: ARMv4T -> ARM7TDMI ARMv5TE -> ARM926EJ-S -> XScale ARMv6 -> ARM1136J(F)-S ARMv6ZK -> ARM1176JZ(F)-S ARMv7A -> Cortex-A8 Cortex-A9 ARMv7M -> Cortex-M3

Hi anyone. When I run make trying to compile Dovecot for a network attached storage box and it fails. I have used two variants of configuration: The first ./configure i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes i_cv_c99_vsnprintf=yes

hello mailinglist, i currently try to compile ffmpeg on a 64bit fedora-core 8 machine using llvm2.3. the "good" things first: everything works fine on a 32bit ubuntu-machine using llvm-2.3 (actually i do not know if that is grace to ubuntu or grace to 32bit) when using the normal gcc on the 64bit fc8 machine, everything works too. now the "bad" thing: it does not work on fc8

Hi,     I am planning to follow the steps to install LLVM for the ARM-target (Processor: Xscale, Architecture: armv5te):   1. Install binutils-2.21 (downloaded from gnu.org)   Steps:   $ ./configure --target=arm-unknown-linux-gnueabi --program-prefix=arm- --prefix =/llvm/arm --with-sysroot=/llvm/arms/sys-root   $ make   $ make install   2. Install LLVM   Steps   $ ../llvm-src/configure

I tried to build VMKit on an ARM device today (a Sheevaplug - armv5te) (native, not cross compiled), and got this error: llvm[3]: Building LLVM assembly with /home/debio/build/vmkit-build/vmkit/lib/Mvm/Runtime/LLVMAssembly.ll /home/debio/build/vmkit-build/vmkit/lib/Mvm/Runtime/LLVMAssembly64.ll ExpandIntegerResult #0: 0x16fbf88: i64,ch = AtomicCmpSwap 0x16e8d84, 0x16fbf00, 0x16fc3c8,

At the last step of building llvm for arm target, I am unable to build llvm-gcc. I am trying the follwing options:   $ ../llvm-gcc/configure --target=arm-linux --enable-pic --program-prefix=llvm- --prefix=/llvm/install --disable-multilib --disable-optimized --enable-bindings =none --enable-llvm=$PWD/../llvm-2.8 --enable-languages=c,c++ --disable-bootstr ap   Then I get the following error when I

Thanks in advance, Are all of the ARM instruction sets that can be specified with -mattr stable? I'm specifically interested in -mattr=+v5te. I'm attempting to build a cross-compiling llvm-gcc to build for Android. The Android native toolchain builds for ARMv5te. --Robb

On 08/02/13 14:42, Renato Golin wrote: [...] > Can you paste the result of a "clang -v -mcpu=CPU file.c" on your box? I > want to see what are the arguments and the assembler/linker it's > choosing to use. What CPU are we talking about? The box itself is an Allwinner A10; armv7l. /proc/cpuinfo says it's got swp half thumb fastmult vfp edsp neon vfpv3. I've been