similar to: Bug-closing protocol

So Reid, you'll be running a BoF on this at the October dev meeting? ☺ --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev Sent: Wednesday, June 20, 2018 6:12 PM To: JVApen at gmail.com Cc: llvm-dev Subject: Re: [llvm-dev] Bug-closing protocol Thanks for taking the time to report bugs! I think you are responsible for filing the most

With the CfP out now, I'm actually motivated to organize a BoF on this topic at the October dev meeting. I haven't put much thought in yet, but think it'd be awesome if we could at least make substantial progress on getting to a bug-closing process/protocol. As one of the people creating bugzilla accounts for new people, I see multiple people requesting an account every day, intending

The 3.6 release is drawing nearer, but the release notes could still use a lot of improvement: LLVM: https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst Clang: https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst The good news is that they can be updated all the way up until release. If you have a patch for the release notes, commit it directly to the

On 18 May 2016, at 07:45, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi everybody, > > I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog. > > However, I can’t omit bike-shedding :) > > Forgive me my directness, but current blog doesn’t look like something close to 2016. > > The

Awful though it may seem, we sometimes do get crashes in the compiler, usually because of some unhandled scenario we never thought of. Unfortunately this typically happens when compiling very large pieces of code, so narrowing down the context of the crash can be difficult. When CLang/LLVM crashes it very helpfully creates a temporary pre-processed file along with a shell script to run this

On Tue, Apr 3, 2012 at 11:37 AM, Jim Grosbach <grosbach at apple.com> wrote: > > On Apr 2, 2012, at 3:07 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > >>> Ah OK. I would have loved to have such a tool, but as a non-clang >>> expert, I can obviously not judge if it is suited. Maybe you are aware >>> of other projects suitable for GSoC,

LLVM Weekly - #157, Jan 2nd 2017 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/157>. Welcome to the one hundred and fifty-seventh 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

Hi all, I'm doing the program slicing [1] in LLVM. Now I implemented the Weiser's algorithm [2] in a simple way by writing a plugin to analyze the IR. My final goal is to slice the source code, thus I recorded all the lines of source code to be sliced. The last step is to delete the lines which are not in the program slice. However, I met a problem when deleting the source code directly:

LLVM Weekly - #52, Dec 29th 2014 =============================== If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/52>. Welcome to the fifty-second 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 Bradbury](http://asbradbury.org).

LLVM Weekly - #57, Feb 2nd 2015 =============================== If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/57>. Welcome to the fifty-seventh 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 Bradbury](http://asbradbury.org).

On Apr 2, 2012, at 3:07 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Ah OK. I would have loved to have such a tool, but as a non-clang >> expert, I can obviously not judge if it is suited. Maybe you are aware >> of other projects suitable for GSoC, > But still many things in "Use clang libraries to implement better > versions of existing

> On May 18, 2016, at 12:59 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > On 18 May 2016, at 07:45, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi everybody, >> >> I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog. >> >> However, I can’t

Hi folks, While building openmpi.4.0.0(Optimized debug build), using trunk clang we encountered a crash(assertion failure). Initially assertion seems trivial: [...] void llvm::DwarfExpression::addFragmentOffset(const llvm::DIExpression*): Assertion `FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"' failed. [...] But, narrowing to RC. We discovered

On 27 August 2017 at 00:01, Alex Bradbury <asb at asbradbury.org> wrote: > Hi all. I'm assuming most people reading this email are familiar with LLVM's > code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> > as well as LLVM Weekly, the development newsletter I've written and sent out > every Monday since Jan 2014. Since that time,

LLVM Weekly - #46, Nov 17th 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/46>. Welcome to the forty-sixth 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 Bradbury](http://asbradbury.org).

> Ah OK. I would have loved to have such a tool, but as a non-clang > expert, I can obviously not judge if it is suited. Maybe you are aware > of other projects suitable for GSoC, But still many things in "Use clang libraries to implement better versions of existing tools" are doable as it seems to me. E.g. delta replacement based on clang. -- With best regards, Anton

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

Hi, maybe you can have a look at the CReduce project: http://embed.cs.utah.edu/creduce/ This project implements many source-to-source transformations of C programs, e.g. removing functions, changing variable names, deleting branches in if-statements, etc. Some of these are purely based on the source code, other use the Clang frontend. Hope this helps, Jonas On Sun, Mar 17, 2013 at 7:25 PM,

LLVM Weekly - #161, Jan 30th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/161>. Welcome to the one hundred and sixty-first 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

LLVM Weekly - #189, Aug 14th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/189>. Welcome to the one hundred and eighty-ninth 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