similar to: [LLVMdev] v[if]cmp

Displaying 20 results from an estimated 200000 matches similar to: "[LLVMdev] v[if]cmp"

2011 Jan 14
0
[LLVMdev] About test suits
Please email the list, not me directly. Try doing a 'make clean' then a 'make VERBOSE=1' in the test-suite directory. -Chris On Jan 13, 2011, at 6:04 PM, Qingan Li wrote: > Hi Chris, > > [qali at qali SingleSource]$ llvm-gcc -v > Using built-in specs. > Target: x86_64-unknown-linux-gnu > Configured with: /home/nicholas/2.8-final/llvmgcc42-2.8.src/configure
2020 Feb 29
2
Multi-Threading Compilers
On Feb 28, 2020, at 8:56 AM, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > On 02/28, Nicholas Krause via llvm-dev wrote: >> Anyhow what is the status and what parts are we planning to move to >> MLIR in LLVM/Clang. I've not seen any discussion on that other than >> starting to plan for it. > > As far as I know, there is no
2020 Mar 18
2
Multi-Threading Compilers
On 3/3/20 8:37 PM, Chris Lattner wrote: > On Feb 28, 2020, at 6:03 PM, Chris Lattner <clattner at nondot.org > <mailto:clattner at nondot.org>> wrote: >> >> On Feb 28, 2020, at 8:56 AM, Johannes Doerfert >> <johannesdoerfert at gmail.com <mailto:johannesdoerfert at gmail.com>> wrote: >>> On 02/28, Nicholas Krause via llvm-dev wrote:
2008 Jun 27
0
[LLVMdev] Implementing llvm.atomic.cmp.swap.i32 on PowerPC
On Jun 27, 2008, at 8:27 AM, Gary Benson wrote: > def CMP_UNRESw : Pseudo<(outs), (ins GPRC:$rA, GPRC:$rB, i32imm: > $label), > "cmpw $rA, $rB\n\tbne- La${label}_exit", > [(PPCcmp_unres GPRC:$rA, GPRC:$rB, imm: > $label)]>; > } > > ...and I can't figure out the syntax for that. Any suggestions? Hi
2017 Sep 27
0
[SPIR-V] SPIR-V in LLVM
On 09/27/2017 05:21 AM, Tomeu Vizoso wrote: > On 07/31/2017 02:30 PM, Nicholas Wilson via llvm-dev wrote: >> >>> On 31 Jul 2017, at 3:23 pm, Neil Henning <ll... at duskborn.com> wrote: >> >> Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a
2020 Mar 19
3
Multi-Threading Compilers
On 3/18/20 9:49 AM, Nicolai Hähnle wrote: > On Wed, Mar 18, 2020 at 7:23 AM Nicholas Krause via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> On 3/3/20 8:37 PM, Chris Lattner wrote: >> >> On Feb 28, 2020, at 6:03 PM, Chris Lattner <clattner at nondot.org> wrote: >> >> >> On Feb 28, 2020, at 8:56 AM, Johannes Doerfert <johannesdoerfert at
2012 Sep 20
0
[LLVMdev] Handling of unsafe functions
On Thu, Sep 20, 2012 at 10:13 AM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > > > On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E > > <javier.e.martinez at intel.com> wrote: > >> We have identified functions in LLVM sources using a static code > analyzer >
2008 Nov 29
0
asterisk-users Digest, Vol 52, Issue 81
I was cleaning and working on laptops most of the day. Check my logs, I did plenty of work. -----Original Message----- From: "asterisk-users-request at lists.digium.com" <asterisk-users-request at lists.digium.com> To: "asterisk-users at lists.digium.com" <asterisk-users at lists.digium.com> Sent: 11/29/2008 1:13 PM Subject: asterisk-users Digest, Vol 52, Issue 81
2012 Sep 24
0
[LLVMdev] Handling of unsafe functions
> I’ll prepare a patch that replaces the string manipulation functions an > appropriate string object. Please break the patch up into focused chunks, one per logical change. We try to keep all LLVM development as incremental as possible [1]. I recommend fixing a single logical occurrence (such as fixing APFloat::convertToHexString()) and then mailing the patch to llvm-commits. It's
2020 Feb 28
3
Multi-Threading Compilers
On 2/28/20 12:56 AM, Chris Lattner wrote: > On Feb 27, 2020, at 9:44 PM, Nicholas Krause <xerofoify at gmail.com > <mailto:xerofoify at gmail.com>> wrote: >> On 2/28/20 12:19 AM, Chris Lattner wrote: >>> Hi Nicholas, >>> >>> You might want to check out MLIR: its pass manager is already >>> automatically and implicitly multithreaded.
2006 Mar 02
0
RE: Asterisk-Users Digest, Vol 20, Issue 13
On Thu, 2006-03-02 at 11:42 -0600, Jordan Novak wrote: > Does anyone have a way to do wake calls? > > > > Jordan Novak > > Communications Technician > > Logistics Health Inc. You could use cron and /var/spool/asterisk/outgoing scripts to dial numbers, etc... > Can you elaborate, I am fairly new to Linux and a phone guy to boot. I am looking for a way for the
2012 Sep 20
3
[LLVMdev] Handling of unsafe functions
On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E > <javier.e.martinez at intel.com> wrote: >> We have identified functions in LLVM sources using a static code analyzer >> which are marked as a “security vulnerability”[1][2]. There has been work >> already done to address some of
2015 Dec 31
0
usbhid-ups dying, consistently
On Dec 31, 2015, at 5:31 PM, Nicholas Leippe <leippe at gmail.com> wrote: > > Is this something to cross post to linux-usb? I guess, although they might need to know some additional details about your libusb configuration (real libusb-0.1.x, or libusb-1.x with libusb-compat). Here is the relevant portion of the code:
2012 Sep 21
5
[LLVMdev] Handling of unsafe functions
>From the responses it's pretty clear that the preference is to avoid using C string functions altogether. I've attached at list of calls in Clang/LLVM. The EASY/MEDIUM/DIFFICULT tag is an estimate of the effort to replace the call based on the location of the source buffer. If there are no objections I'll prepare a patch that replaces the string manipulation functions an
2008 Jun 27
2
[LLVMdev] Implementing llvm.atomic.cmp.swap.i32 on PowerPC
Hi all, I'm trying to figure out how to add the instructions required for llvm.atomic.cmp.swap.i32 on PowerPC. I figured out LWARX (patch attached) but the other two (CMP_UNRESw and STWCX) require multiple instructions: let Defs = [CR0] in { def STWCX : Pseudo<(outs), (ins GPRC:$rS, memrr:$dst, i32imm:$label), "stwcx. $rS, $dst\n\tbne-
2009 Aug 23
2
[LLVMdev] configure/cmake help :)
Hi All, I have two small things that I would appreciate some help with: 1. Config/Alloca.h is now dead. Once configure and cmake support is removed, we can zap it. Can someone remove the cmake/autoconf stuff that pokes at Config/Alloca.h? 2. Daniel's regex email. I think the right answer is to just autodetect whether regcomp/regexec etc are available (his #2). Could someone add
2009 Aug 24
0
[LLVMdev] configure/cmake help :)
Chris Lattner <clattner at apple.com> writes: > 1. Config/Alloca.h is now dead. Once configure and cmake support is > removed, we can zap it. Can someone remove the cmake/autoconf stuff > that pokes at Config/Alloca.h? AFAIK, there is nothing specific for include/llvm/Config/alloca.h on the cmake build and it works fine after removing the file (checked on Linux x86_64).
2011 Jan 13
2
[LLVMdev] About test suits
Hi sir, I have built the test suits in following steps: 0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-* platform*.tar.gz | tar -xvf - 1. $cd SRC_DIR/llvm-2.8/projects 2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite 3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols
2015 May 19
2
[LLVMdev] [RFC] Upstreaming LLVM/SPIR-V converter
> On May 19, 2015, at 1:25 AM, Neil Henning <llvm at duskborn.com> wrote: > > The problem is - as Sean and Pete (and others before) have pointed out, from a users perspective they'll want to say 'clang make me SPIR-V'. There are things in SPIR-V that are not representable by the LLVM IR, so we'd have to add SPIR-V specific intrinsics for this (again making the case
2015 May 16
3
[LLVMdev] [RFC] Upstreaming LLVM/SPIR-V converter
2015-05-16 6:42 GMT+01:00 Chris Lattner <clattner at apple.com>: > > > On May 15, 2015, at 9:53 AM, Chris Bieneman <beanz at apple.com> wrote: > > > > +1 to lib/Target/SPIRV/(Reader|Writer) > > > > I really like this idea. I’ve talked with some people on both the LLVM and Khronos sides and I really think adding SPIR-V support to LLVM as an optional