search for: smul

Hi! I'm not sure how to handle intrinsic functions that have non-i32 operands. The target only supports 32-bit registers natively but for some operations, only the lower 16 bits are significant. For example, the SMULS instruction does a 16 x 16 fractional multiply with saturation. I've defined an intrinsic function: int __builtin_opus_smuls(short a, short b); def int_opus_smuls : GCCBuiltin<"__builtin_opus_smuls">,     Intrinsic<[llvm_i32_ty], [llvm_i16_ty, llvm_i16_ty],     [IntrNoMem...

> Why? I'd prefer we avoid introducing even more special cases. Is there > any reason why we should not define "complex <scalar type>", or to be > more restrictive, "complex <floating-point type>"? I really don't like > the idea of excluding 128-bit complex types, and I think that we can > have a generic facility. Hal, we had 128-bit

...readcyclecounter @llvm.bitreverse @llvm.eh.begincatch @llvm.eh.endcatch @llvm.eh.padparam @llvm.stackprotector @llvm.stackprotectorcheck @llvm.objectsize @llvm.donothing Words with dots: @llvm.sadd.with.overflow @llvm.uadd.with.overflow @llvm.ssub.with.overflow @llvm.usub.with.overflow @llvm.smul.with.overflow @llvm.umul.with.overflow @llvm.convert.to.fp16 @llvm.convert.from.fp16 @llvm.eh.typeid.for @llvm.init.trampoline @llvm.adjust.trampoline @llvm.masked.load @llvm.masked.store @llvm.masked.gather @llvm.masked.scatter @llvm.lifetime.start @llvm.lifetime.end @llvm.invariant.start @...

> wow... Tell me, what cross compiler can I use for ARM if I am working in a i686-Linux machine? As usual - gcc + binutils. > At the same time, how I can simulate it? QEMU ? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi, I want to add an extra instruction to the Alpha ISA. This is not a new operation; it is just an addition with a lower latency, let's call it fast-add. Could you give me advice on what's an easy and clean approach to this? I am thinking of adding an extra instruction to the LLVM IR to represent this fast-add operation (I want to make the decision of using either the normal addition

wow... Tell me, what cross compiler can I use for ARM if I am working in a i686-Linux machine? At the same time, how I can simulate it? But the way, If I deleted the unknown pseudo-op and change section .rodata definition, I can use my stone age cross compiler. I am just wondering why it works without them. Thanks in advance. On Thu, Jun 18, 2009 at 4:26 PM, Anton Korobeynikov <anton at

...; apt-get install -y --no-install-recommends ncurses-bin > /dev/null > fi > > RED="$(${SETTPUT} setaf 1)" > NORMAL="$(${SETTPUT} sgr0)" > GREEN="$(${SETTPUT} setaf 2)" > YELLOW="$(${SETTPUT} setaf 3)" > UNDERLINE="$(${SETTPUT} smul)" > WHITE="$(${SETTPUT} setaf 7)" > BOLD="$(${SETTPUT} bold)" > > message() { > printf "%40s\n" "${WHITE}${BOLD}$*${NORMAL}" > } > good() { > printf "%40s\n" "${GREEN}$*${NORMAL}" > } > error() { >...

add object rules so that the division, remainder and friends get really build on sparc, patch from Fabio M. Di Nitto <fabbione@ubuntu.com>. reworked to apply on latest git tree. Signed-off-by: maximilian attems <maks@sternwelten.at> --- Has been since long in the Debian and Ubuntu klibc. diff --git a/klibc/arch/sparc/Makefile.inc b/klibc/arch/sparc/Makefile.inc index

...t0.S | 2 usr/klibc/arch/sparc/crt0i.S | 100 +++++++++++ usr/klibc/arch/sparc/divrem.m4 | 276 +++++++++++++++++++++++++++++ usr/klibc/arch/sparc/pipe.S | 30 +++ usr/klibc/arch/sparc/setjmp.S | 38 ++++ usr/klibc/arch/sparc/smul.S | 160 +++++++++++++++++ usr/klibc/arch/sparc/syscall.S | 19 ++ usr/klibc/arch/sparc/sysfork.S | 25 +++ usr/klibc/arch/sparc/sysstub.ph | 25 +++ usr/klibc/arch/sparc/umul.S | 193 ++++++++++++++++++++ 21 files changed, 1540 in...

...e, &__sigreturn); +} diff --git a/usr/klibc/arch/sparc/Kbuild b/usr/klibc/arch/sparc/Kbuild index d013f5d4..d92bbb0f 100644 --- a/usr/klibc/arch/sparc/Kbuild +++ b/usr/klibc/arch/sparc/Kbuild @@ -8,7 +8,7 @@ targets := crt0.o m4-targets := sdiv.o srem.o udiv.o urem.o klib-y := $(m4-targets) smul.o umul.o __muldi3.o -klib-y += setjmp.o pipe.o syscall.o sysfork.o +klib-y += setjmp.o pipe.o sigaction.o syscall.o sysfork.o klib-y += ../../libgcc/__ashldi3.o ../../libgcc/__ashrdi3.o klib-y += ../../libgcc/__lshrdi3.o ../../libgcc/__divdi3.o diff --git a/usr/klibc/arch/sparc/sigaction.c b/us...

...o-install-recommends ncurses-bin > /dev/null >> fi >> >> RED="$(${SETTPUT} setaf 1)" >> NORMAL="$(${SETTPUT} sgr0)" >> GREEN="$(${SETTPUT} setaf 2)" >> YELLOW="$(${SETTPUT} setaf 3)" >> UNDERLINE="$(${SETTPUT} smul)" >> WHITE="$(${SETTPUT} setaf 7)" >> BOLD="$(${SETTPUT} bold)" >> >> message() { >> printf "%40s\n" "${WHITE}${BOLD}$*${NORMAL}" >> } >> good() { >> printf "%40s\n" "${GREEN}$*${NORMAL}&...

On 05/04/2019 09:37, Simon Pilgrim via llvm-dev wrote: > On 04/04/2019 14:11, Sander De Smalen wrote: >> Proposed change: >> >> ---------------------------- >> >> In this RFC I propose changing the intrinsics for >> llvm.experimental.vector.reduce.fadd and >> llvm.experimental.vector.reduce.fmul (see options A and B). I also >> propose renaming

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: