similar to: [LLVMdev] Test - Please Ignore

This is a test message, please ignore it. Reid

Testing .. Please Ignore. Reid.

Okay I have put a #ifdef HAVE_RLIMIT_RSS round the RSS code. There needs to be logic added to config system to complement this. Or shall I just use an #ifdef _CYGWIN_ ? Regarding the Bytecode writer stuff. I will try adding some inline dis-ambiguator functions. Aaron ----- Original Message ----- From: "Reid Spencer" <rspencer at reidspencer.com> To: "LLVM Developers

Hi Aaron, On Sun, 2007-02-18 at 20:43 +0000, Aaron Gray wrote: > Hi Reid, > > Cygwin 'sys/resource.h' has get/setrlimit() functions support for > RLIMIT_DATA and RLIMIT_AS but not RLIMIT_RSS. Then, please fix it to not use RLIMIT_RSS in the cygwin case. Perhaps you should just use RLIMIT_AS for cygwin. It will trigger sooner than RLIMIT_RSS but that's probably okay.

Hello, Reading through this, I found a typo... In the paragraph after the 3rd code snippet in the 1st question's section: "The second operand will be the field offset" seems like it should be the third operand? The second is the pointer offset... HTH! =] -Chandler Carruth On 8/15/06, Reid Spencer <rspencer at reidspencer.com> wrote: > > All, > > The often

This just in from Oscar .. Reid -------- Forwarded Message -------- > From: Oscar Fuentes <ofv at wanadoo.es> > To: Reid Spencer <rspencer at reidspencer.com> > Subject: Re: svn issues > Date: Wed, 25 Jul 2007 19:09:17 +0200 > > Reid Spencer <rspencer at reidspencer.com> writes: > > > Hi David, > > > > On Wed, 2007-07-25 at 10:38 -0500,

On Mon, 07 Aug 2006 19:36:01 -0700 Reid Spencer <rspencer at reidspencer.com> wrote: > > Hi Simon, > > What version of llvm-gcc did you configure LLVM with? If you don't > know, please send your configure.out file from your LLVM_OBJ_ROOT I didn't find that file in the source anywhere. Also, I don't normally use llvm-gcc, so I didn't knowingly configure for

All, The often misunderstood GetElementPtr (GEP) instruction now has its own FAQ document. For all of you that have struggled with understanding how this instruction works, hopefully this document will make it clear and help you with your use of LLVM. Many thanks to Chris Lattner for setting me straight on how this instruction works and reviewing the document. Document Link :

On Sun, 2007-02-18 at 21:42 +0000, Aaron Gray wrote: > Okay I have put a #ifdef HAVE_RLIMIT_RSS round the RSS code. > > There needs to be logic added to config system to complement this. > > Or shall I just use an #ifdef _CYGWIN_ ? Please just use #ifdef _CYGWIN_ > > Regarding the Bytecode writer stuff. I will try adding some inline > dis-ambiguator functions. Yeah,

Ok, so if I needed very precise control over the allocation of memory, then I should avoid using integers with bit widths larger than 64 bits (or perhaps 128)? Is there a hard rule for an integer being stack allocated, ie. one that doesn't depend on the current implementation details? Sandro On 6/18/07, Reid Spencer <rspencer at reidspencer.com> wrote: > Sandro Magi wrote: > >

Hi Reid, Cygwin 'sys/resource.h' has get/setrlimit() functions support for RLIMIT_DATA and RLIMIT_AS but not RLIMIT_RSS. Aaron ----- Original Message ----- From: "Reid Spencer" <rspencer at reidspencer.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Sunday, February 18, 2007 8:32 PM Subject: Re: [LLVMdev] LLVM Cygwin build

All, Just to be really clear. The web-site already says this, but .. Despite this message: On Wed, 2007-04-11 at 19:17 -0700, Reid Spencer wrote: > Hi Scott, > > Only attendees can get the T-Shirt as there isn't funds to > ship them all over the place. > > Reid. If you can't attend the meeting you can still get a T-Shirt but you'll have to pay the shipping

On Thu, 2006-12-07 at 22:00 -0800, Chris Lattner wrote: > On Dec 6, 2006, at 10:44 AM, Andrew Lenharth wrote: > > > Currently, Structure layout is left to targets, which implement them > > according to the ABI of that platform. While this is fine for most > > structures, it makes packed structures very ugly. All fields in a > > packed type must be converted to byte

On 3/11/07, Reid Spencer <rspencer at reidspencer.com> wrote: > Could you submit the patch? We could make sure that 2.0 doesn't have the > same problem. Sure, I can't test this from where I am now but if anyone can take it for a spin to test it and verify the fix then by all means check it in. I'm just providing a hand-edited diff from our vendor branch here (1.9 tarball

I can't make it on the 22nd, but I will be there if it's on the 29th. Ryan Brown On 3/23/07, Reid Spencer <rspencer at reidspencer.com> wrote: > Hi Sarah, > > On Fri, 2007-03-23 at 15:11 -0700, Sarah Thompson wrote: > > I'll almost certainly come along, possibly with one or two other NASA > > people. > > Great! If/when you know their names, have them

On Fri, 2007-04-13 at 17:11 -0500, Vikram S. Adve wrote: > TSG (our support group) is going to set up a Wiki on zion so that > access can be checked against a list of some sort. What does that mean exactly? Will the users be authenticated? If not, this isn't acceptable .. spam. What wiki is being set up? > It should happen > by early next week, perhaps sooner (not

Hi Scott, On Wed, 2007-04-11 at 18:31 -0700, Scott Michel wrote: > +2 Large T-shirts (me and Mark Thomas, also from Aerospace). Are you confirming Mark Thomas as attending then? Only attendees can get the T-Shirt as there isn't funds to ship them all over the place. Reid. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at

You can get one for free on code.google.com. It comes as part of code hosting. Authentication/authorization for both wiki and svn is governed by the same credentials as given by the project owner(s) (the wiki is driven by the same svn repo as the code). So even hosting svn there might be a good thing . On 4/14/07, Reid Spencer <rspencer at reidspencer.com> wrote: > On Fri, 2007-04-13 at

On Mon, 18 Jun 2007, Sandro Magi wrote: > Ok, so if I needed very precise control over the allocation of memory, > then I should avoid using integers with bit widths larger than 64 bits > (or perhaps 128)? Is there a hard rule for an integer being stack > allocated, ie. one that doesn't depend on the current implementation > details? In the generated code, or in the compiler

On 2/23/07, Reid Spencer <rspencer at reidspencer.com> wrote: > > However, if I run the AutoRegen.sh script (after modifying it to > > accept autoconf 2.61, which I think is fine as gentoo slots it the > > same as the 2.5[0-9] versions), the configure no longer works: > > ~/programming/llvm-1.9/projects/zhe $ cd autoconf/ > >