search for: reviewcorner

...enough people have the time or > willingness to review code, no amount of signal boosting is going to improve > things. Seeing as the idea got positive feedback, I'm going to trial it starting from next week. Please submit patches which are awaiting review here <http://llvmweekly.org/reviewcorner>. Let's start simple and see if it works. I've suggested the following guidelines for submitting a code review thread for inclusion: * The patch has gone at least two weeks without substantial review feedback OR this is your first patch to an LLVM project * You have updated the patch bas...

...lvmweekly.org> and pass it on to anyone else you think may be interested. Please send any tips or feedback to <asb at asbradbury.org>, or @llvmweekly or @asbradbury on Twitter. ## Review corner >From next week, I'm going to give the ['review corner'](http://llvmweekly.org/reviewcorner) idea a try. If you have patches that have been stuck without any meaningful review for two weeks or more (or are making your first contribution to an LLVM project), please submit them for inclusion. This is an experiment - we're going to see how it works out and fine-tune the details as we go....

Hello all, I recently felt the need to have debug info at the LLVM IR level (because my frontend's semantics vastly differ from IR that it doesn't make much sense to use it). Asm can sometimes be too "low level", so it's nice to have the ability to single-step at the IR level. The pass that used to do this (-debugir) bitrotted and was removed from tree. I spent the weekend

https://reviews.llvm.org/D41659 Implemented missing trigonometric optimization in llvm. Here we have implemented the following missing trigonometric optimizations. 1. tan(x)*cos(x)=sin(x) 2. sin(x)*cos(x) = sin(2*x)/2 3. sin(x)/tan(x)=cos(x); 4. tan(x)/sin(x)=1/cos(x); -------------- next part -------------- An HTML attachment was scrubbed... URL:

...directives meaning this change improves link time by around 15%. [r321470](https://reviews.llvm.org/rL321470). ## Review corner The LLVM Weekly review corner serves to highlight patches that are stuck waiting awaiting review, or work from first-time contributors. See [here](http://llvmweekly.org/reviewcorner) for more information and how to submit you work for inclusion. Of course the hope is that highlighting these patches will enable LLVM Weekly readers will step up and help to get them merged. I'll be reporting back each week on any activity generated on these patches, as well as sharing a new b...

...0). * LLDB gained a new class for handling process environments. [r322174](http://reviews.llvm.org/rL322174). ## Review corner The LLVM Weekly review corner serves to highlight patches that are stuck waiting awaiting review, or work from first-time contributors. See [here](http://llvmweekly.org/reviewcorner) for more information and how to submit you work for inclusion. Of course the hope is that highlighting these patches will enable LLVM Weekly readers will step up and help to get them merged. I'll be reporting back each week on any activity generated on these patches, as well as sharing a new b...

...ed to consider a new policy for when the bitcode backwards compatibility "guarantee" can be changed. ## Review corner The LLVM Weekly review corner serves to highlight patches that are stuck waiting awaiting review, or work from first-time contributors. See [here](http://llvmweekly.org/reviewcorner) for more information and how to submit you work for inclusion. Of course the hope is that highlighting these patches will enable LLVM Weekly readers will step up and help to get them merged. I'll be reporting back each week on any activity generated on these patches, as well as sharing a new b...

...std.org/JTC1/SC22/WG21/docs/papers/2016/p0202r1.html). [r322489](http://reviews.llvm.org/rL322489), and others. ## Review corner The LLVM Weekly review corner serves to highlight patches that are stuck waiting awaiting review, or work from first-time contributors. See [here](http://llvmweekly.org/reviewcorner) for more information and how to submit you work for inclusion. Of course the hope is that highlighting these patches will enable LLVM Weekly readers will step up and help to get them merged. I'll be reporting back each week on any activity generated on these patches, as well as sharing a new b...

...ject commits Nothing notable this week (that I spotted at least - tips on patches to include always welcome). ## Review corner The LLVM Weekly review corner serves to highlight patches that are stuck waiting awaiting review, or work from first-time contributors. See [here](http://llvmweekly.org/reviewcorner) for more information and how to submit you work for inclusion. Of course the hope is that highlighting these patches will enable LLVM Weekly readers will step up and help to get them merged. I'll be reporting back each week on any activity generated on these patches, as well as sharing a new b...

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, it's provided something of a "signal boost" for important mailing list discussions and

...umentation has been updated. > [r319213](http://reviews.llvm.org/rL319213). > > > ## Review corner > > The LLVM Weekly review corner serves to highlight patches that are stuck > waiting awaiting review, or work from first-time contributors. See > [here](http://llvmweekly.org/reviewcorner) for more information and how to > submit you work for inclusion. Of course the hope is that highlighting > these > patches will enable LLVM Weekly readers will step up and help to get them > merged. I'll be reporting back each week on any activity generated on these > patches, a...