similar to: [LLVMdev] Re: LLVM Bugzilla broken?

Reid Spencer wrote: > John, > > The rsyncd doesn't seem to be up. See the attached email. The mirror > tries to sync every 30 minutes and this is what I'm getting from the > cron job. This was from the sync attempted at 2:12pm (PDT) today. I think I got it working. Can you try it again and let me know if it works? Thanks. -- John T. > > Reid. > > John

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,

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

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,

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

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.

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: > >

On Mon, 17 Nov 2003, Reid Spencer wrote: > I've noticed in the last day that I'm not getting any Bugzilla email any > more. I haven't changed my settings in Bugzilla. Did something change > at UIUC? I don't think so... I'm still getting plenty of bugzilla mail. :) -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

Reid Spencer wrote: > FYI, > > Yesterday's Slashdot had an article about Linux compiler benchmarks from > Coyote Gulch (Scott Ladd). In this update he compares GCC and ICC. You > can read the article here: > http://www.coyotegulch.com/reviews/linux_compilers/ > > Of particular note was his use of SciMark 2.0 which is a NIST developed > benchmark for scientific

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

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

Chris Lattner wrote: > On Mon, 16 Aug 2004, Reid Spencer wrote: > > >>That didn't fix it. Same problem. >> >>Perhaps rsyncd is not being run by xinetd? Can you see if its started? >>Check to see if there is a /etc/init.d/rsyncd file. If there is, and its >>not already running, try: >> /etc/init.d/rsyncd start >>otherwise: >>

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

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

Reid Spencer wrote: >There are some bugs against it that state the current progress. The >problem is that it depends on how the libraries are being used. Even if >you get past the linking problems, you will end up with re-registration >of passes and options, etc., which causes asserts. So, for now, there >aren't many good solutions. > > Is it possible to link opt and

Reid Spencer wrote: > On Wed, 2004-08-04 at 12:21, John Criswell wrote: > >>In regards to Misha's comments about the automatic execution of bytecode >>files, there are several ways to do it: >> >>1) Have bytecode files start with #!<JIT/llee/whatever> (portable) >>2) Encapsulate with ELF >>3) Register the type with the kernel (Linux only)

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

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

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

Yes, that's my understanding, too. But I'm not controlling where my library -ldbghelp is put when g++ is called. I just put it in the TOOLLINKOPTS variable in Makefile.config. Henrik >From: Reid Spencer <reid at x10sys.com> > >John Criswell wrote: >> >>It seems that the -L path options are specified before the LLVM libraries >>(libSystem and