similar to: [LLVMdev] Forward of moderated message

An embedded message was scrubbed... From: kapil at iitk.ac.in Subject: Help regarding LLVM IR Date: Wed, 18 Aug 2004 22:31:41 +0530 (IST) Size: 1833 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040818/584b1397/attachment.mht>

An embedded message was scrubbed... From: Mudit Jain <muditjain1987 at gmail.com> Subject: Application inquiry in GSOC 2010 Date: Fri, 19 Mar 2010 21:55:13 -0700 Size: 4700 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100321/fe1ab90e/attachment.mht>

llvm-bounces at cs.uiuc.edu wrote: > > ------------------------------------------------------------------------ > > Subject: > Fw: (by sospeng at tom.com)something is wrong , when compiling llvm on debian > From: > "4" <sospeng at tom.com> > Date: > Mon, 29 Aug 2005 20:05:46 +0800 (CST) > To: > llvmdev at cs.uiuc.edu > > To: > llvmdev at

Is it safe to use the LLVM cfrontend 1.6 with LLVM 1.7 or the latest LLVM from CVS? I am running OS X 10.3.9, which I believe corresponds to Darwin kernel version 7.9.0. When I tried to use the 1.7 cfrontend, I could not get LLVM 1.7 or the LLVM from CVS to compile. However, when I used the 1.6 cfrontend (which is additionally labeled Darwin 7.9.0), I was able to get them to compile.

Hi, I was wondering whether anyone has attempted to port LLVM to windows running with a POSIX layer, such as cygwin? I recently tried to build and run llvm on cygwin, and I got the llvm tools working. There were a few problems in the configure script, namely the mmap test fails due to MAP_FIXED not working on windows (all other mmap() stuff works), which I simply commented out since its

Hi, If you read the troubleshooting section carefully and actually look at your mic and speaker signals, it should be obvious why it doesn't work: http://www.speex.org/docs/manual/speex-manual/node7.html#SECTION00741000000000000000 Cheers, Jean-Marc P.S. Next time, please post links to your files instead of attaching the files, as there is a message size limit on the mailing list.

[forwarded without attachments, for real this time] > Begin forwarded message: > > From: Gabriele TAORMINA <gabriele.taormina at legrand.com <mailto:gabriele.taormina at legrand.com>> > Subject: Re: [Nut-upsdev] Adding drivers to NUT? > Date: August 27, 2018 at 6:03:55 AM EDT > To: Daniele Pezzini <hyouko at gmail.com <mailto:hyouko at gmail.com>> >

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

Hello! I was looking around for a solution which would allow me to un-forward already locally forwarded port but had no luck. So I decided to try and add it myself. I am not a good C coder, in fact, I've never really coded under unix before(it's just half a year since I fully moved from windowz). Here is what I made by now:

Hi, When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got the following error : -------------------------------Compilation error listing if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi make GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc -B/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/

Your message dated Wed, 13 Sep 2006 10:34:57 +0200 with message-id <20060913083457.GA11942@wavehammer.waldi.eu.org> and subject line fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB:

On Tue, 4 May 2004, Chris Lattner wrote: > I suspect that a large reason that LLVM does worst than a native C > compiler with the CBE+GCC is that LLVM generates very low-level C code, > and I'm not convinced that GCC is doing a very good job (ie, without > syntactic loops). Yup, this is EXACTLY what is going on. I took this very simple C function: int Array[1000]; void test(int

This is a forward of a question from the SourceForge LLVM forum. If anyone has experience with Cygwin and building the C front-end there, please reply and CC Alex. --- Post by Alex Vinokur below --- =============== Windows 2000 GNU gcc 3.3.3 (cygwin special) =============== ./configure ./make I have got compilation error ------------------------------- make[1]: Entering directory

Jeff, Actually, that was my fault. I forgot to remove the non-existent directories from the configure.ac file. That's done and committed now, so the advice is still the same: update configure script :) Reid. On Sun, 2004-09-05 at 09:53, Jeff Cohen wrote: > Configure gives me these errors on FreeBSD. I'm proceding with the build anyway to see what happens. Don't worry :)

On Tue, 28 Jun 2005, John Criswell wrote: > addPass(PM, createSimplifyLibCallsPass()); // Library Call Optimizations > > Rebuild gccas. Then, try to build the LLVM GCC frontend again. Please email > the llvmdev list and let us know if it works. > > In the meantime, I will continue to try to get a reduced test case and either > fix the bug or hand it off to Reid (the

On Sun, 05 Sep 2004 10:49:44 -0700 Reid Spencer <reid at x10sys.com> wrote: > Jeff, > > Actually, that was my fault. I forgot to remove the non-existent > directories from the configure.ac file. That's done and committed > now, so the advice is still the same: update configure script :) > > Reid. OK, no problems building. I got some minor issues with the simple

On May 4, 2004, at 10:36 PM, Chris Lattner wrote: > On Tue, 4 May 2004, Chris Lattner wrote: >> I suspect that a large reason that LLVM does worst than a native C >> compiler with the CBE+GCC is that LLVM generates very low-level C >> code, >> and I'm not convinced that GCC is doing a very good job (ie, without >> syntactic loops). > > Yup, this is

So, I'm trying to build everything from source for the Debian package for LLVM, including the C/C++ front end. I'm running this build on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar

> Okay, I took a closer look at your output. > > I was correct in that gccas is attempting to assemble a native PPC > assembly language file. However, this appears to be happening because > the assembly file is generated by the GCC Makefiles for libgcc2 (in > llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). > > The first thing I would try is Marco's suggestion: add

On Fri, 30 Apr 2004, Patrick Flanagan wrote: > Thanks! Grabbed the latest from CVS and added that linker option to the > config file. It looks like it compiles and runs the SPEC tests ok now. Great! > Just to make sure I understand how LLVM works, got a few clarifications: > > 1. The ppc code I'm generating with the -native-cbe is static, correct? Yes, it's purely static