similar to: [LLVMdev] Bugzilla Working Again

Dear All, I've fixed a problem with Bugzilla. Various perl modules were not installed on the new system. I've copied them over from the old system, and as far as I can tell, the bug tracker is working again. -- John T. -- John T. Criswell jcriswel at bigw.org "It's today!" said Piglet. "My favorite day," said Pooh.

Devang Patel wrote: > > On Dec 17, 2007, at 2:01 PM, John Criswell wrote: > >> Devang Patel wrote: >>> >>> On Dec 17, 2007, at 1:47 PM, John Criswell wrote: >>> >>>> Dear Devang Patel, >>>> >>>> In response to your comment on bug 1868, how do I get BottomPass to >>>> requires Pass2 before Pass1? Is it by

Dear Devang Patel, In response to your comment on bug 1868, how do I get BottomPass to requires Pass2 before Pass1? Is it by reversing the order of the calls to AU.addRequired()? -- John T. -- John T. Criswell jcriswel at bigw.org "It's today!" said Piglet. "My favorite day," said Pooh.

Sean Peisert wrote: > John, > > I may be missing something here, but if I the compilation docs, I need > to build LLVM first and the C frontend second. But doing this, I > get: > > **llvm-gcc/llvm-g++ was not found, > > (obviously -- it wasn't installed, right?) You do need to build LLVM first before building llvm-gcc. This may seem a bit weird, but

Dear LLVM Developers, The LLVM website, CVS repository, and SAFECode website should now be back online. Should you encounter any problems with the LLVM services, please send email to llvmdev at cs.uiuc.edu so that we may fix it. Regards, John T. Criswell ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu

Hi, It looks like the CVS server is still not available. When I try to update with cvs, I get: cvs [update aborted]: connect to llvm-cvs.cs.uiuc.edu(128.174.245.58):2401 failed: Connection refused I know the server was down earlier this week but according to the message below, its supposted to be restored by now. Could someone please help? Thanks, Reid. On Wed, 2004-01-07 at 14:30, John T.

Dear All, Our main server is back up, and all LLVM services (CVS, website, etc) should be up and available for use. If you notice that something is wrong, please send an email to llvmdev at cs.uiuc.edu. Thanks! -- John T. -- ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu * * Research Programmer

Dear All, Do people think that they are ready to create the LLVM 1.6 release branch? I believe all the development is pretty much done. Is all the documentation in the LLVM source tree updated and ready? I'm not able to make a full doc review like I've been able to do in previous releases, so I need volunteers to work on the docs if they're not done yet. -- John T. -- John

Alexander Friedman wrote: > On May 17, John Criswell wrote: > >>Dear All, >> >>I've finished building binaries for the GCC frontends and am now testing >> the 1.5 release branch on i386/Linux, Sparc/Solaris, and PowerPC/MacOS X. >> >>I'm looking for volunteers to test LLVM 1.5 on platforms that we don't >>have in house. I'm

Chris Morgan wrote: > Any reason not to upgrade to subversion? It does a much better job > with handling moved or renamed files although svn doesn't actually > store a 'move' or a 'rename' as a single versioned operation. We discussed moving to another revision control system about a year ago, if I recall correctly. At that time, we decided not to move to another

Dear All, Here is a more complete list of regressions for the platforms listed below. Some of the regressions from the previous list I emailed a few days ago have been fixed or were false positives. Thanks to all who've helped fix things. We would like to try to get as many of these fixed as possible before I create the release branch (still scheduled for tomorrow, Friday). I'll

Cyrille Mescam wrote: > Morning, > > I would like to know if you received my mail with the assembly code > you wanted. > > It not, i'll send it again to you. > > Thanks for your help. > > Regards. > > Cyrille > I've looked into the files you sent me, and it seems that the problem is occuring due to the C library simplication pass (which is run

Hi John, Please see below, too >From: John Criswell <criswell at cs.uiuc.edu> >Date: Tue, 27 Jul 2004 14:57:02 -0500 > >Henrik Bach wrote: >>Hi, > >Please see below. > >> >>I get this error: >>------------------ >>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >>ToolRunner.cpp:396: error: (Each

Ricardo wrote: > Hello, > > Is PA working on the macintosh already? Although we may not have run it on MacOS X recently, I believe that it should work. We've run it on several architectures and operating systems, including SparcV9/Solaris. If you find that PA doesn't compile or work on MacOS X, please file a bug report (http://llvm.cs.uiuc.edu/bugs/) so that we can fix it.

Thanks for the explanation. It's more clear now The only thing that seems strange is that in the function llvm_expand_shortcircuit_truth_expr in the front end, there is the creation of a PHI instruction. If there is no SSA yet, why do you do that? Thanks in advance --- John Criswell <criswell at cs.uiuc.edu> wrote: > Ricardo wrote: > > Hi, > > > > I have been

Chris Lattner wrote: > On Thu, 12 May 2005, John Criswell wrote: > >> Here is a more complete list of regressions for the platforms listed >> below. Some of the regressions from the previous list I emailed a few >> days ago have been fixed or were false positives. Thanks to all >> who've helped fix things. >> >> We would like to try to get as many

On Mon, 22 Mar 2004, Umar Janjua wrote: > Well, I compiled release but it gave error while making png library. > > The inclusion of zlib.h in the file png.h cannot locate file zlib.h. > If you change the inclusion to > > include "../zlib/zlib.h" instead of just "zlib.h" in png.h > > then compilation succeeds. I haven't seen a reply to this on LLVM

Who takes action on this? >From: John Criswell <criswell at cs.uiuc.edu> >Date: Wed, 01 Sep 2004 15:16:53 -0500 > >Henrik Bach wrote: >>Reid, >> >>>Well, if it doesn't break anything else, I'd fix the header file. The >>>standard type name is supposed to uint64_t not u_int64_t. I would just >>>change the header file to define both

Henrik Bach wrote: >> From: John Criswell <criswell at cs.uiuc.edu> >> Date: Mon, 25 Oct 2004 15:38:52 -0500 > > >> >> When you run configure, you'd do something like this: >> >> configure --prefix=<...> LDFLAGS="-L<path where libdgbhelp is installed" >> >> If you modify Makefile.config directly, just add the

On Thu, 8 Jan 2004, Grant Gould wrote: Dear Mr. Gould, > Is there any documentation of the llvm bytecode format? I looked > around the website but didn't see any; did I miss some obvious > document? At this time, we do not have any documentation on the bytcode format. I believe one LLVM user was working on such a document at one time, but if so, it is not complete. One option