[flang-dev] Flang round-table at 2019 LLVM dev meeting

Doerfert, Johannes via flang-dev flang-dev at lists.llvm.org
Sat Oct 19 10:18:49 PDT 2019


That is unfortunate (for me).

It also conflicts with the 2:35 time slot (not only the 2pm one), which includes
 Panel: Inter-procedural Optimization (IPO)

(I didn't realize this based on your initial mail.)

@Hal, I will find another moderator for the panel if we keep this slot.

________________________________________
From: flang-dev <flang-dev-bounces at lists.llvm.org> on behalf of Stephen Scalpone via flang-dev <flang-dev at lists.llvm.org>
Sent: Saturday, October 19, 2019 11:54
To: via flang-dev
Subject: Re: [flang-dev] Flang round-table at 2019 LLVM dev meeting

Tanya scheduled the flang rountable for Tuesday, October 22, from 2pm until 3:10pm at the 2019 LLVM Developers’ Meeting.

Please share any topics you’d like to discuss with the list or just bring ‘em along.  See you there!

- Steve


From: flang-dev <flang-dev-bounces at lists.llvm.org> on behalf of Stephen Scalpone via flang-dev <flang-dev at lists.llvm.org>
Reply-To: Stephen Scalpone <sscalpone at nvidia.com>
Date: Monday, October 7, 2019 at 9:22 AM
To: via flang-dev <flang-dev at lists.llvm.org>
Subject: [flang-dev] Flang round-table at 2019 LLVM dev meeting

Hi all,

Tanya has just posted the sign-up sheet for round tables at the 2019 LLVM dev meeting.  She’s asked that we provide a request for two time slots -- a first and second choice – as well as a duration.  We can ask for 35 or 70 minutes; I propose we ask for 70 just to give us the freedom to talk as long as we need.

There are a couple of times that look good to me because they conflict with talks that don’t obviously interest flang developers. Please propose a different time if you’d like.  Let’s see if we can reach consensus and schedule a time.

Thanks,

- Steve

2pm Tuesday, conflicts with
- LTO for Swift
- LLVM_Reduce for testcase reductions

11:55am Wednesday, conflicts with
- Making UB hurt less: security mitigations through automatic variable initialization
- Souper-Charging Peepholes with Target Machine Info
- The Penultimate Challenge: Constructing bug reports in the Clang Static Analyzer

________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________


More information about the flang-dev mailing list