similar to: LLVM Social - Paris: January 30th, 2018

Displaying 20 results from an estimated 1100 matches similar to: "LLVM Social - Paris: January 30th, 2018"

2020 Apr 22
3
_ExtInt, LLVM integers and constant time
> On Apr 22, 2020, at 12:24 AM, Roman Lebedev via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Wed, Apr 22, 2020 at 9:35 AM Adrien Guinet via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> Hello everyone, >> >> After reading the nice blog post about _ExtInt, I was wondering whether >>
2020 Apr 22
2
_ExtInt, LLVM integers and constant time
Hello everyone, After reading the nice blog post about _ExtInt, I was wondering whether operations on i128/i256 and more generally on integer types in LLVM are guaranteed to be constant time or not. For instance, for now, the x86 & aarch64 backend generate constant time code for additions on i256 integers (see https://godbolt.org/z/xMfkqz & https://godbolt.org/z/jbkSpe), but is there
2017 Jun 17
5
LoopVectorize fails to vectorize loops with induction variables with PtrToInt/IntToPtr conversions
Hello all, There is a missing vectorization opportunity issue with clang 4.0 with the file attached. Indeed, when compiled with -O2, the "op_distance" function get vectorized, but not the "op" one. For information, this test case has been reduced from a file generated by the Pythran compiler (https://github.com/serge-sans-paille/pythran). If we take a look at the generated
2017 Jun 20
3
LoopVectorize fails to vectorize loops with induction variables with PtrToInt/IntToPtr conversions
On 06/20/2017 03:26 AM, Hal Finkel wrote: > Hi, Adrien, Hello Hal! Thanks for your answer! > Thanks for reporting this. I recommend that you file a bug report at > https://bugs.llvm.org/ Will do! > Whenever I see reports of missed optimization opportunities in the face > of ptrtoint/inttoptr, my first question is: why are these instructions > present in the first place? At
2012 Jun 08
1
[LLVMdev] Paris LLVM Meetup 26. June at IRILL (with clang bug squashing)
On Tuesday, 26. June, an LLVM Meetup will take place in Paris. We invite everybody interested in LLVM to join. o What is LLVM? LLVM is a collection of modular and reusable compiler and toolchain technologies. It is used as the base of many modern compilers such as clang (C/C++/Objective-C), GHC (Haskell), dragonegg (Ada, Fortran, ...), several commercial OpenCL compilers or RenderScript.
2017 May 30
1
LLVM Social - Paris: June 14th, 2017
The next LLVM social in Paris will happen on June 14th, 2017. Everyone interested in LLVM, Clang, lldb, Polly, lld, ... is invited to join. Event details, including registration (free but mandatory) at http://www.meetup.com/LLVM-Clang-social This edition will be particularly busy (and interesting !) as we are delighted to welcome 3 guest speakers: - Hal Finkel (Argonne National Laboratory)
2020 May 18
2
Use Galois field New Instructions (GFNI) to combine affine instructions
On 5/18/20 8:24 PM, Craig Topper wrote: > I can tell you that your avx512 issue is that v64i8 gfni instructions also > require avx512bw to be enabled to make v64i8 a supported type. The C > intrinsics handling in the front end know this rule. But since you > generated your own intrinsics you bypassed that. Indeed that's the issue... I was stick with what Intel announces here
2020 Oct 08
4
__attribute__((apple_abi)): targeting Apple/ARM64 ABI from Linux (and others)
Hello everyone, I made a quick patch to clang/llvm to introduce an "apple_abi" function attribute (https://github.com/aguinet/llvm-project/commit/c4905ded3afb3182435df30e527955031cb0d098), to be able to compile functions for the Apple ARM64 ABI when targeting other ARM64 OSes (e.g. Linux). This can be seen as the Apple version of the already existing "ms_abi" attribute. In
2019 Nov 28
2
SLP example not being vectorized
Hi, I am new to llvm with a particular interested in the optimization area, specially on SLP. While working through the tutorial, I ran this example [1] with the hope to see SLP vectorization in action but for some reason, I do not see it on the LLVM assembly as seen below. Is there anything I am missing? I am using Clearlinux as build machine and this has clang version 9.0.0.
2018 Feb 05
0
LLVM Weekly - #214, Feb 5th 2018
LLVM Weekly - #214, Feb 5th 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/214>. Welcome to the two hundred and fourteenth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex
2016 Jan 22
2
Testing an LLVM pass
Hi all, I’m currently writing an LLVM function pass and I want to know how can I test it? Currently, I try to compile some crypto library and check if the test suite are working but I don’t think this is very efficient. Does anyone has a leads? Greetings, Johan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature
2007 Dec 26
1
Visit to Melbourne in January
Hi all, I''ll be in Melbourne, Australia from January 24th until February 2nd, for LinuxConf Australia and a bit of vacation. James Turnbull is going to organize a meetup during the trip, so ping James at james@lovedthanlost.net if you''re going to be in .au and are interested in joining us. Cheers, Luke -- Never interrupt your enemy when he is making a mistake.
2011 Apr 05
0
[LLVMdev] instrument a byte code with llvm
On 4/5/11 11:36 AM, Nabila ABDESSAIED wrote: > > > 2011/4/5 John Criswell <criswell at illinois.edu > <mailto:criswell at illinois.edu>> > > On 4/5/11 11:22 AM, Nabila ABDESSAIED wrote: >> hi, >> I'm newer in llvm >> i would like to instrument a byte code with a pass and as a >> result i would like to get an
2018 Dec 10
2
Migrate utils/ Python 2 scripts to Python 3
On Fri, Nov 30, 2018 at 03:25:10PM +0100, Serge Guelton via llvm-dev wrote: > On Thu, Feb 01, 2018 at 04:47:03PM -0500, James Y Knight via llvm-dev wrote: > > That said, I do think it could make sense to prepare llvm for the world in > > which "python" is python3 on some systems. So, I'd propose the following: > > 1. Change all #! lines to say
2019 Dec 31
2
Bay Area social ‼️MOVED‼️ January 2nd
Hi folks, The LLVM Bay Area social needs to move from Tied House because they closed. We’ll be across the street at Steins beer garden on January 2nd, 7PM, ask for “LLVM”. Please pass the word along so everyone makes it to the right place! We’ll figure out something longer term. JF
2020 Jan 29
5
[RFC] Python 2 / Python 3 status
Hi folks, Python2 has reached end of support[0], and many core Python packages are dropping pthon 2 support[1]. This is a subject that raises periodically on this mlist, with a rather strong no in 2018 [-1] and a slow move in 2019 [-2, -3]. Even if Python is not a core build requirement, it's used during some configurations steps (e.g. in the cmake export_executable_symbols function), for
2011 Apr 05
4
[LLVMdev] instrument a byte code with llvm
hi, I'm newer in llvm i would like to instrument a byte code with a pass and as a result i would like to get an instrumented byte code. i would like that a pass add a method (which calculate the number of instructions) in the end of each block. the instrumented code should contain in each block a method that calculate the number of instructions Please Help me thank you -- Nabila ABDESSAIED
2020 Jul 16
2
[RFC] Pass return status
> Out of curiosity, does change here include changes to names, and other semantically-irrelevant changes (e.g., changing the order of operands in a PHI)? The hashing function used to detect changes is currently very simple: it only accounts for instruction opcode and order. So some semantically-irrelevant changes are ignored (as well as some relevant changes), and some are not. Permuting two
2020 Jul 15
3
[RFC] Pass return status
Hi folks, some more information on this feature - as a reminder I started one month ago to work on an expensive check that would verify that pass return status is correctly reported by passes, i.e. no pass return « IR not modified » while actually modifying it. It took ~20 pass fixes to achieve that goal, as many passes were not respectful of that contract, but as of
2019 Dec 03
5
clang and -D_FORTIFY_SOURCE=1
Hi folks (CCing llvm-dev, but that's probably more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only partial: https://pagure.io/fesco/issue/2020 I dig into the glibc headers in