similar to: BoF: Enhancing LLVM's Floating-Point Exception and Rounding Mode Support

Hi all, As you probably know, we’ll meet on the first day of the conference, right before lunch, to discuss about a possible move of our hosting to Git/GitHub, and consider the various options and associated tradeoff (Schedule entry here: http://sched.co/8Yzj <http://sched.co/8Yzj> ) I’d like to remind you that the detail of the proposals and the variants is online here:

Hi, I am not sure if this is the right mailing list to ask my question, if not, please refer me to the proper one. Is there any support for rounding modes in LLVM floating point? I looked in the assembler reference manual, and it doesn't seem so. I am thinking about choosing LLVM as one of the backends for my programming language Babel-17 (www.babel-17.com). Babel-17 features interval

Dear community, In preparation for the BoF on Parallel IR at the US developers meeting we would like to collect feedback from the whole community. The concerns, ideas, etc. will be summarized in the BoF and should provide a good starting point for a discussion. We know that over the years the topic of a parallel extension for LLVM was discussed on the mailing list [0, 1, 2], workshops [3, 4] or

Dear community, We are trying to setup a BoF ( Raising Next Generation of LLVM Developers, http://sched.co/8Yzs). In our academic-oriented environments the main work force is students: undergrads, grads or PhD (rarely postdocs). Often we have limited time to bring somebody up to speed and we have to it in a productive and motivating for both parties way. I believe most of you had

Hi all, During the review of https://reviews.llvm.org/D65997 an issue was revealed, which relates to the decision of how compiler should represents constrained floating point operations. If a floating point operation requires rounding mode or exception behavior different from the default, it should be represented by constrained intrinsic (

Hi, Next week at the developers meeting, I'm chairing a BoF session on improving our performance tracking and benchmarking infrastructure. I'd like to make the most out of the 45 minute slot. Therefore, I'd like to start the discussion a bit earlier here, giving everyone who can't come to the BoF a chance to put in their 2 cents. At the same time, I hope this will also give me a

Which optimization did you find unsafe? Thanks, --Serge ср, 21 авг. 2019 г. в 05:12, Cameron McInally <cameron.mcinally at nyu.edu>: > On Tue, Aug 20, 2019 at 1:02 PM Serge Pavlov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi all, >> >> During the review of https://reviews.llvm.org/D65997 >>

Hi, On Thu, 28 Jul 2016 09:32:18 -0700 Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think David and I are probably the most familiar with how WinEH works in > LLVM, but I don't think either of us has time to prepare a talk for the dev > meeting. I'm trying to prepare a talk on supporting the MS debug info > format in LLVM this year. That said,

All, I have arranged for an LLVM BoF at SC13 in Denver: http://sc13.supercomputing.org/schedule/event_detail.php?evid=bof143 If you will be at SC13, have an interesting project based on or within LLVM, and would be willing to come to the BoF and spend 10 minutes or so giving an overview of it, please email me. I am trying to get a collection of people together to talk about vectorization and

Yes, you’re probably right about this. I was originally thinking of FENV_ACCESS as a fully strict mode of operation, but what you’re suggesting aligns with what Cameron suggested and even some of my own reasoning on other points. So, let me amend my previous proposal to say: STDC FENV_ACCESS {ON|OFF} Patch in progress. I think ON should force the following: except_behavior { strict }

Folks, Next Thursday evening (20 July) we''ll be holding a "Xen Users BOF" at the Ottawa Linux Symposium. >From the BOF description: "The Xen Users'' BOF will provide an interactive forum for users to talk about their experiences with Xen and highlight some of the cool configurations they have created with it. This will also be an opportunity for newcomers to

Folks, Next Thursday evening (20 July) we''ll be holding a "Xen Users BOF" at the Ottawa Linux Symposium. >From the BOF description: "The Xen Users'' BOF will provide an interactive forum for users to talk about their experiences with Xen and highlight some of the cool configurations they have created with it. This will also be an opportunity for newcomers to

Hi I am late to the party. Here is my personal take of the topic: * Do you ship software as IR today? What lessons have you learned? Yes. We accept AppStore submission in bitcode (LLVM IR). The core function in clang is upstreamed and you can look up the related code path triggered by -fembed-bitcode option. * Challenges of shipping software as IR Compatibility: We are trying to enhance the

I thought people on this list might be interested in the Xen Developer Summit in Edinburgh in October (alongside LinuxCon EU and a bunch of other confs). Lars tells me that they are going to be advertising more widely next week so if you are interested now would be a good time to sign up. Ian. -------- Forwarded Message -------- Dear Community member, the schedule for the Xen Project

Hi folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

Hi folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

Yup that is quite similar to my use case, but in addition I use LLVM to JIT as well from C using MCJIT. I have a patch for a DIBuilder binding, but it does change the API a bit, so depending on how this discussion goes, it can or cannot be added. It was necessary as the current binding wrap all metadata in values, which is very wasteful when dealing with a large amount of metadata. The breakage

Hi LLVM’ers! We are hosting a BoF at this year's Dev Meeting on a subject we hope will be of interest to some (many?) of you: shipping software (entirely) as LLVM IR. You can find our proposal in the meeting schedule online: https://llvmdevelopersmeetingbay2016.sched.org/event/8Yzq/shipping-software-as-llvm-ir The BoF is scheduled to last 45 minutes, which will go by very quickly! To make

Hi, We are going to have a BoF session on vectorization on Nov 8th. Everybody is invited! Most of the BoF is going to be an open discussion, but Hal and I are also going to talk a little bit about the Loop vectorizer, the BB vectorizer and the common infrastructure. Here is a preliminary agenda for the BoF: 1. A quick overview on vectorization in LLVM - 3 min. 2. Loop vectorizer design

Dear Michael & Hal, We had a submission to SC13 on beating OpenACC compilers with LLVM+Polly+NVPTX [1]. Unfortunately, reviewers somehow expected we want to go into polyhedral tools intercomparison, which was absolutely not our goal. The goal was exactly to bring a competitive HPC/GPU toolchain for end users. Only NV works for now, MIC is in progress. If you think this contribution is worth a