search for: theraven

On 5 June 2012 19:48, David Chisnall <theraven at theravensnest.org> wrote: > We plan on holding the next Cambridge LLVM social on Wednesday the 20th of June, from 7:30pm onwards, in The Cambridge Blue: Hi David, Is this today? Are you guys still going? --renato

On 20 Jun 2012, at 17:21, Renato Golin wrote: > On 5 June 2012 19:48, David Chisnall <theraven at theravensnest.org> wrote: >> We plan on holding the next Cambridge LLVM social on Wednesday the 20th of June, from 7:30pm onwards, in The Cambridge Blue: > > Hi David, > > Is this today? Yes. > Are you guys still going? I am, and I believe others are... David

...rote: > Seems to be a known bug in SVN 1.8.0, can you try upgrading to 1.8.1 or downgrading to 1.7? Downgrading to 1.7.x means that I can't access my local repo, since there is no svn downgrade. Upgrading to 1.8.1 gives: svn: E175002: Unable to connect to a repository at URL 'https://theraven at llvm.org/svn/llvm-project/llvm/trunk' svn: E175002: Unexpected HTTP status 400 'Bad Request' on '/svn/llvm-project/llvm/trunk' David

Hello again LLVM people in Cambridge (or London, or places similarly easily accessible on the train), We plan on holding the next Cambridge LLVM social on Wednesday the 20th of June, from 7:30pm onwards, in The Cambridge Blue: http://www.the-cambridgeblue.co.uk/blueroadmap.html The pub does food as well as beer, so at least some of us will be eating there. I hope to see you there, David

On Wed, Jun 20, 2012 at 5:23 PM, David Chisnall <csdavec at swan.ac.uk> wrote: > On 20 Jun 2012, at 17:21, Renato Golin wrote: > >> On 5 June 2012 19:48, David Chisnall <theraven at theravensnest.org> wrote: >>> We plan on holding the next Cambridge LLVM social on Wednesday the 20th of June, from 7:30pm onwards, in The Cambridge Blue: >> >> Hi David, >> >> Is this today? > > Yes. > >> Are you guys still going? > > I a...

Hi, When I try to use LLVM svn (with svn 1.8.0), I'm currently seeing this: svn: E175004: The PROPFIND response did not include the requested properties Does anyone else have this problem? David

On 20.08.2013, at 11:16, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > Hi, > > When I try to use LLVM svn (with svn 1.8.0), I'm currently seeing this: > > svn: E175004: The PROPFIND response did not include the requested properties > > Does anyone else have this problem? Seems to be a known bug in SVN 1.8.0, can you try upgrading to 1.8.1 or

My friend Veslot proposed me the Raven ! http://www.teteamodeler.com/allopass/images/corbeau.jpg As a matter of fact the intelligence of this bird is comparable to one of a monkey, although its brain is close to a reptile brain. R is quite the same : small, compact, but so clever. This is a canadian website explaining (in french) the R-aven intelligence

On Fri, Mar 30, 2018 at 1:56 AM, David Chisnall <theraven at theravensnest.org> wrote: > On 29 Mar 2018, at 21:25, Michael Spencer via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > There's been some desire recently to start writing documentation in > Markdown instead of reStructuredText. I put up a [patch]( &gt...

On 17 Dec 2010, at 03:15, Michael Spencer wrote: > As long as EFI C isn't radically different from normal C, I would > suggest adding a EBC target to LLVM first. Otherwise you have no way > to test the clang modifications. As was stated in the last post on this subject, EFI C has integer types that have a size determined at run time. I can't see how this would be integrated

Hello any LLVM people in or near Cambridge (the original one, not the knock-off in Massachusetts), Chandler's closing speech at EuroLLVM indicated that LLVM developers on this side of the pond don't spend as much time in the pub as our Californian counterparts and that this was an important thing to address. To address this, I propose that we start a regular Cambridge LLVM social. The

On Thu, Dec 16, 2010 at 5:42 PM, Lu Mitnick <king19880326 at gmail.com> wrote: > Hello all, > > I want to the do followings: > > (1) Modify the LLVM front-end(clang) to support EFI C > > (2) Add EFI Byte Code target to LLVM > > I am wondering to know which task should I do first, modify front end or > porting LLVM? > > thanks > > yi-hong As long as

Hi Everyone, This is off-topic, so please feel free to disregard it, but I'm sending it to this list in the hope that it will reach a largish number of users. I am currently looking at updating some of our advocacy material (which advertises exciting new features like SMP support), and before I do I'd like to get a better feel for why the rest of you are using FreeBSD. If you had to

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful

On 29/04/2019 21:12, Joe Maloney wrote: > With CFT version you chose to build, and package individual components such as sendmail with a port option. That does entirely solve the problem of being able to reinstall sendmail after the fact without a rebuild of the userland (base) port but perhaps base flavors could solve that problem assuming flavors could extend beyond python. This sounds very

Hi Vincent, This is an LLVM issue, rather than a clang issue, so llvmdev is the appropriate mailing list for this report. Your fix looks semantically valid, but it would be cleaner to only create and destroy the pthread_rwlockattr_t if it is actually needed, rather than creating it, initialising it, not using it, and then destroying it on mingw (and, as the code currently stands, *BSD). The

Hi Bill, For the GNU runtimes, this metadata is stored in the module structure in each compilation unit, and uses a different set of flags. Do you have any plans for this to be generic, or is it intended just for Darwin? David On 19 Jan 2012, at 23:33, Bill Wendling wrote: > Hi Sandeep, > > ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses