search for: iwmmxt

...We are working on marvell pxa310 (bought from Intel), and with the tools chain from marvell, I comple klibc as follows: klibc-1.5> ln -s /home/zjujoe/svn/mhlv_2.6/working/songlixin/20081007_kernel_tflashupdate/ linux klibc-1.5>cat 1.sh export KLIBCARCH=arm export CROSS_COMPILE=arm-iwmmxt-linux-gnueabi- klibc-1.5>. ./1.sh klibc-1.5>make KLIBCCC usr/klibc/__static_init.o KLIBCCC usr/klibc/vsnprintf.o ? LIST usr/klibc/syscalls/klib.list LIST usr/klibc/klib.list KLIBCAR usr/klibc/libc.a KLIBCLD usr/klibc/libc.so arm-iwmmxt-linux-gnueabi-ld: ERROR: Sour...

...arch valid or not,before we throw it to the > parser,which can be used for both arm > and aarch64. For the actions I mentioned above,I wrote a check function as below, basing on the naming rules of the arm architecture. +//Only if -march startwith "armv" or "v" or "iwmmxt" or "xscale",it can be seen valid and sended to TargetParser +//for further parsing +static bool checkArchValid(StringRef Arch) +{ + if ((Arch.startswith("armv")) || Arch[0] == 'v' || + (Arch.startswith("iwmmxt")) || (Arch.startswith("xscale&...

...2.3 the error looks as follows: ./ffmpeg_g -i 1minute.mov -an -y /tmp/1minute.avi FFmpeg version SVN-r14075, Copyright (c) 2000-2008 Fabrice Bellard, et al. configuration: --disable-ffserver --disable-ffplay --disable-mmx --disable-mmx2 --disable-ssse3 --disable-armv5te --disable-armv6 --disable-iwmmxt --disable-altivec --disable-network --disable-ipv6 --disable-zlib --disable-vhook --disable-stripping --extra-cflags=-emit-llvm -c --extra-ldflags=-emit-llvm -c --enable-cross-compile --cross-prefix=llvm- libavutil version: 49.7.0 libavcodec version: 51.58.0 libavformat version: 52.16.0 lib...

On 5 May 2016 at 13:01, Bradley Smith <Bradley.Smith at arm.com> wrote: > Allowing -march=aarch64/arm64 is somewhat misleading I think, -march is used > for specifying an architecture version to target whereas aarch64/arm64 don’t > convey any information to that effect, does it mean armv8a, armv8.1-a, etc? Hi Bradley, That's a good point. But also, what does "armv8a"

...Win32 target ci: Remove MESON_TESTTHREADS workaround ci: Pin gcovr version to 7.x ci: Don't execute failing jobs ci: Add auto_cancel policy ci: Disable coverage for arm-v5 and mipsel targets Matt Turner (3): Post-release version bump to 0.43.5 iwmmxt: Drop support Pre-release version bump to 0.44.0 Mike Hommey (1): pixman: Adjust arm assembly for binutils change Peter Hutterer (1): ci: add workflow rules to allow for MR pipelines f wasil (2): RISC-V floating point operations Fixed memory leak in tests...

....000000000 +0300 +++ configure 2006-12-15 02:02:36.669912494 +0300 @@ -2144,12 +2144,7 @@ fi fi -# detect sse support -if "$unixtests/sse.test" "$TEST_COMPILER" "$OPT_VERBOSE"; then - CFG_HAVE_SSE=no -else - CFG_HAVE_SSE=yes -fi +CFG_HAVE_SSE=no # check iwmmxt support if [ "$CFG_IWMMXT" = "yes" ]; then I've configured Qt with -no-exceptions -no-stl -static. I haven't tried shared built yet. Probably, enabling exception will break the build, since llvm-gcc4 does not support exceptions well yet. 3. Workaround some llvm-gcc4 &...

I wrote a proof of concept regarding the cpu capabilities runtime detection and choice of optimized function. I follow design which had been discussed on IRC. Also, i notice a little drawback: we must propagate the arch index through functions which don't have codec state as argument. However, if it's look good, i will continue to implement it. Best regards, -- Aur?lien Zanelli

On 16 September 2015 at 21:56, Jim Grosbach <grosbach at apple.com> wrote: > Why do we care about GAS? We have an assembler. It's not that simple. There are a lot of old code out there, including the Linux kernel which we do care a lot, that only compiles with GAS. We're slowly moving the legacy code up to modern standards, and specifically some kernel folks are happy to move up