search for: minus_on

...=================================================== --- include/llvm/CodeGen/ValueTypes.h (revision 66504) +++ include/llvm/CodeGen/ValueTypes.h (working copy) @@ -21,6 +21,8 @@ #include "llvm/Support/DataTypes.h" #include "llvm/Support/MathExtras.h" +static const uintptr_t minus_one = -1; + namespace llvm { class Type; @@ -92,7 +94,10 @@ iPTR = 255, // LastSimpleValueType - The greatest valid SimpleValueTypevalue. - LastSimpleValueType = 255 + LastSimpleValueType = 255, + + // force the size of the enum to be sizeof(uintptr_t)...

...============================================= --- include/llvm/CodeGen/ValueTypes.h (revision 66504) +++ include/llvm/CodeGen/ValueTypes.h (working copy) @@ -21,6 +21,8 @@ #include "llvm/Support/DataTypes.h" #include "llvm/Support/MathExtras.h" +static const uintptr_t minus_one = -1; + namespace llvm { class Type; @@ -92,7 +94,10 @@ iPTR = 255, // LastSimpleValueType - The greatest valid SimpleValueTypevalue. - LastSimpleValueType = 255 + LastSimpleValueType = 255, + + // force the size of the enum to be sizeof(uintptr_t)...

Hello, > +static const uintptr_t minus_one = -1; -1 here is of signed int type. What if you will use -1ULL ? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...] #endif const Type *LLVMTy; }; This works on my big endian 64-bit system but I've not seen what damage it may do on other platform types. On 4/7/09 4:09 PM, "Anton Korobeynikov" <anton at korobeynikov.info> wrote: > Hello, > >> +static const uintptr_t minus_one = -1; > -1 here is of signed int type. What if you will use -1ULL ?

On Fri, Feb 6, 2009 at 8:42 PM, Tanya Lattner <tonic at nondot.org> wrote: > LLVMers, > > The 2.5 pre-release is available for testing: > http://llvm.org/prereleases/2.5/ > I'm updating the Fedora packaging of LLVM, and with the 02/20 prerelease it fails to build on ppc64: http://koji.fedoraproject.org/koji/taskinfo?taskID=1148023 make[1]: Entering directory

Hi, > llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td > tblgen: IntrinsicEmitter.cpp:163: void EmitTypeForValueType(std::ostream&, > llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' > failed. this came up before IIRC, but I don't remember the details - buggy system compiler? Try searching the archives. Also, if you

...ine C_MUL_NEON(m, a, b, t, ones, tv) \ + do{ \ + t = vrev64q_f32(b); \ + m = vmulq_f32(a, b); \ + m = vmulq_f32(m, ones); \ + t = vmulq_f32(a, t); \ + tv = vtrnq_f32(m, t); \ + m = vaddq_f32(tv.val[0], tv.val[1]); \ + }while(0) + +#define ONES_MINUS_ONE 0xbf8000003f800000 //{-1.0, 1.0} +#define MINUS_ONE 0xbf800000bf800000 // {-1.0, -1.0} + +static void kf_bfly4_neon_m1(kiss_fft_cpx *Fout, int N) { + float32x4_t Fout_4[2]; + float32x2_t Fout_2[4]; + float32x2_t scratch_2[2]; + float32x2_t ones_2 = vcreate_f32(ONES_MINUS_ONE); + float32x2_t...

Hi, I am beginning the porting process for Linux on System z (aka IBM Mainframe). I thought I¹d build LLVM first with the c and cpp backends so that tools like TableGen would be created that I¹d then use to process the .td files that I¹ll be creating. So I used svn to grab the code from the repository and ran configure and make. However, the build breaks at this point: llvm[1]: Building

Hello, This patch introduces ARM NEON Intrinsics to optimize kf_bfly4 routine in celt part of libopus. Using NEON optimized kf_bfly4(_neon) routine helped improve performance of opus_fft_impl function by about 21.4%. The end use case was decoding a music opus ogg file. The end use case saw performance improvement of about 4.47%. This patch has 2 components i. Actual neon code to improve

...t; This works on my big endian 64-bit system but I've not seen what damage it > may do on other platform types. > > > On 4/7/09 4:09 PM, "Anton Korobeynikov" <anton at korobeynikov.info> wrote: > > > Hello, > > > >> +static const uintptr_t minus_one = -1; > > -1 here is of signed int type. What if you will use -1ULL ? > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >

...ate tmp = - let g = new G.guestfs () in - if trace () then g#set_trace true; - if verbose () then g#set_verbose true; + let g = open_guestfs () in g#disk_create ~backingfile:indisk ?backingformat:format ~compat:"1.1" tmp "qcow2" Int64.minus_one @@ -180,9 +176,7 @@ You can ignore this warning or change it to a hard failure using the (* Connect to libguestfs. *) let g = - let g = new G.guestfs () in - if trace () then g#set_trace true; - if verbose () then g#set_verbose true; + let g = open_guestfs () in (* Note...

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make

This still isn't working at the moment. See: http://marc.info/?t=139457409300003&r=1&w=2 This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. Rich.

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

...if trace then g#set_trace true; - if verbose then g#set_verbose true; + if trace () then g#set_trace true; + if verbose () then g#set_verbose true; g#disk_create ~backingfile:indisk ?backingformat:format ~compat:"1.1" tmp "qcow2" Int64.minus_one @@ -186,8 +186,8 @@ You can ignore this warning or change it to a hard failure using the (* Connect to libguestfs. *) let g = let g = new G.guestfs () in - if trace then g#set_trace true; - if verbose then g#set_verbose true; + if trace () then g#set_trace true; + if verbose...

.. and a lot of refactoring. https://bugzilla.redhat.com/show_bug.cgi?id=1167623 Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=1167623