similar to: [LLVMdev] New Attributes API

On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 Feb 2013, at 01:32, Bill Wendling wrote: > >> No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes haven't made it there though). > > The attributes API has

On 6 Feb 2013, at 07:50, Bill Wendling wrote: > On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 5 Feb 2013, at 01:32, Bill Wendling wrote: >> >>> No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes

Hi LLVMers, We're actively working on finishing up the release, which has been delayed. Last week was dominated by several paper submissions which were all due at about the same time, so the release fell behind (if you're interested, the papers are available on the main page). We are currently shooting for getting the release out the door early next week. That said, we have made a lot

It is very exciting to see experimental Windows support listed for 3.3. Is there documentation somewhere that tracks what works and what doesn't in this configuration, particularly for C++?. Otherwise it is difficult for those not actively involved in developing Windows support to know what to expect when experimenting. Thanks, Andrew On Mon, Apr 1, 2013 at 5:05 PM, Bill Wendling

On Feb 6, 2013, at 2:31 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 6 Feb 2013, at 07:50, Bill Wendling wrote: > >> On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: >> >>> On 5 Feb 2013, at 01:32, Bill Wendling wrote: >>> >>>> No. It hasn't been written up. We typically

On Fri, Apr 4, 2008 at 2:38 AM, Bill Wendling <isanbard at gmail.com> wrote: > On Apr 2, 2008, at 10:11 PM, Xuehai Qian wrote: > > Hi LLVMers, > > I am a PHD student in CS dept in UIUC, I am doing a project for > > Vikram's course, it is about PRE. I would like to know why you didn't > > choose SSAPRE in LLVM, since it seems to be more suitable for

Happy April! [Contrary to the day, this is not an April Fool's joke. ;-)] It has been several months since the release of Clang 3.2. Now is the time to start thinking about the next release! The (very) tentative schedule is testing in May and a release in June. What This Means For You Now is the time to start thinking about which features you are currently working on and getting them

On Apr 2, 2008, at 10:11 PM, Xuehai Qian wrote: > Hi LLVMers, > I am a PHD student in CS dept in UIUC, I am doing a project for > Vikram's course, it is about PRE. I would like to know why you didn't > choose SSAPRE in LLVM, since it seems to be more suitable for LLVM (it > can operate directly on SSA form and avoid the conversion between SSA > and bit-vector). Can

On Feb 7, 2013, at 2:25 PM, Bill Wendling <wendling at apple.com> wrote: > On Feb 7, 2013, at 12:14 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> The comment on other VCSs seems irrelevant, but if you are making such invasive changes that they must be done in multiple passes then either a feature branch and a merge or a local git clone seem the correct

On Feb 8, 2013, at 12:59 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 7 Feb 2013, at 22:25, Bill Wendling wrote: > >>>> You don't understand what I'm saying. The APIs were changing way too quickly for it to make sense to create such a document. I tried as best as I could to mitigate all of the problems, but there were several intermediate steps

FYI: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I

On Feb 23, 2009, at 8:40 PM, Nick Lewycky wrote: > For those of you who haven't noticed, I'm planning to commit a major > change to the Makefile rules tomorrow evening (Tuesday) if there are > no complaints about it between now and then. > > This needs testing on Darwin. I've heard back from Linux on many > platforms and even FreeBSD, which is fantastic, but

On Feb 7, 2013, at 12:14 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 6 Feb 2013, at 20:20, Bill Wendling wrote: > >> You don't understand what I'm saying. The APIs were changing way too quickly for it to make sense to create such a document. I tried as best as I could to mitigate all of the problems, but there were several intermediate steps that had

On Feb 6, 2013, at 2:02 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Bill Wendling <wendling at apple.com> writes: > > [snip] > >> Welcome to living on the top-of-tree! :-) >> >> We are in between releases. It's expected that the APIs will be >> unstable. [snip] > > One thing is an unstable API, and a different thing is a code base

Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there

Hi Sean, I think it can go in as it is. It's a good start. Thanks, Joe! -bw On Feb 9, 2013, at 9:46 PM, Sean Silva <silvas at purdue.edu> wrote: > This looks like a good starting point. I would prefer to call it HowToUseAttributes.rst though (it is essentially a HowTo). > > Bill, is it ok to commit this, or would you like cook up something different to go into the docs?

I recently reimplemented the Attributes class. It now hides the data representation inside of an opaque class. In the near future, we will be extending this class to encompass many other attributes. The changes pose one problem, however. The C-API still uses the old data representation for passing along the Attributes class. In particular, these two functions: LLVMAttribute

Hi Dmitry, I can try my best, but it would be a bit tricky to get it all finished by then... -bw On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > Bill, > > Are there any chances that you complete it before 3.4 is branched? > > > On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at

Hi Bill, On 18/10/12 10:35, Bill Wendling wrote: > I recently reimplemented the Attributes class. It now hides the data representation inside of an opaque class. In the near future, we will be extending this class to encompass many other attributes. > > The changes pose one problem, however. The C-API still uses the old data representation for passing along the Attributes class. In

Cool I renamed it, per Sean's suggestion, to HowToUseAttributes. Committed as r174961 The doc should be live now: http://llvm.org/docs/HowToUseAttributes.html Cheers, Joe Abbey On Feb 12, 2013, at 3:26 AM, Bill Wendling <wendling at apple.com<mailto:wendling at apple.com>> wrote: Hi Sean, I think it can go in as it is. It's a good start. Thanks, Joe! -bw On Feb 9,