similar to: [LLVMdev] New PowerPC GCC Frontend

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.

John, Thanks for the information. That comment in the source code confused me and I wanted to be sure that the installation of all the LLVM framework in the macintosh for testing the pool allocation was not going to be done in vain. The LLVM documentation states that gcc 3.4x is necessary for compiling the LLVM. On the other hand, Xtools 1.5 for Mac includes only gcc 3.3 and Xtools 2.0 includes

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 All, Thanks to the testing done by Bill Wendling, we have the following list of regressions for PPC: TEST (cbe) 'exception_spec_test' FAILED! ******************** TEST (cbe) 'function_try_block' FAILED! ******************** Oopack (jit, llc, and cbe) also fails, but I don't know if that's a regression or not. I'm alright with releasing with these regressions

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

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.

Steven M. Carr wrote: > I am trying to install llvm with gcc 3.2.2-5 and I get a number of > errors in stl include files. I have attached the mess of errors that I > get. If you know of a stupid oversight that might cause this, let me know. > > Steve > > > ------------------------------------------------------------------------ > > Are you sure that you are

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

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

Long Fei wrote: > > I am investigating some inlining issue, so I did > > llvm-gcc aaa.c bbb.c ... nnn.c -o output > opt -inline -inline-threshold=xxx < output.bc | llc -march=c > > output_inline.c I am unsure of whether the LLVM GCC frontend does any inlining. However, I do know that your methods above run the LLVM inlining pass, albeit indirectly. If you use

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

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, I would like to create the release branch for the llvm-gcc source code tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty healthy and no one is currently doing any development on it. If there's something that needs to be fixed, or you're working on llvm-gcc, please email the list so that I can delay creating the branch as appropriate. I won't be

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

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

Misha Brukman wrote: > On Wed, Aug 18, 2004 at 12:16:04AM +0400, Valery A.Khamenya wrote: > >>Building PowerPC.td register information header with tblgen >>Included from PowerPC.td:22: >>Parsing PowerPCInstrInfo.td:53: Variable not defined: 'GPRC'! >>make[3]: *** [PowerPCGenRegisterInfo.h.inc] Error 1 >>make[3]: Leaving directory

You should download and install in the first shot: a.. LLVM source code (3.5M) f.. GCC Front End Source Code (30.0M) Then follow the items listed in http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html for Cygwin. Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com

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

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