similar to: [LLVMdev] Are 'make check' failures of interest in llvm-gcc?

On Nov 15, 2007, at 11:24 AM, Török Edwin wrote: > Hi, > > I have run 'make check' in llvm-gcc 4.0 (svn version). > I got some failures, mostly gcc.apple tests fail (and a gcc.c-torture > test, namely 20000804-1.c) > > Are these tests of any interest to llvm-gcc itself, or they are > problems > with "upstream" ? (gcc 4.0). > If the former, should

On 2009-07-15 23:24, Dale Johannesen wrote: > On Jul 15, 2009, at 11:52 AMPDT, Stuart Hastings wrote: > > >> We've had a lot of churn in all the trunks (llvm, llvm-gcc, clang) >> recently, and the testing buildbots have been failing repeatedly. >> >> I spoke with Chris this AM, and he suggested we have a "stabilization >> day." Please avoid

--- On Fri, 1/30/09, Török Edwin <edwintorok at gmail.com> wrote: > From: Török Edwin <edwintorok at gmail.com> > Subject: Re: [LLVMdev] [LLVM][g++] A helping hand > To: kasra_n500 at yahoo.com, "LLVM Developers Mailing List" <llvmdev at cs.uiuc..edu> > Date: Friday, January 30, 2009, 8:29 AM > On 2009-01-30 18:19, Kasra wrote: > > Hi All, >

Thanks Edwin. I found DebugInfo.cpp may be useful. Could you tell me which function I should call inorder to know the source file name and the line number for a particular instruction? Cheers, Zheng 2010/5/18 Török Edwin <edwintorok at gmail.com>: > On 05/18/2010 01:26 PM, Zheng Wang wrote: >> Hello, >> >> Could I get some debug info at the byte code level? I am

This is the name of a structure in the source code. 2009/10/30 Török Edwin <edwintorok at gmail.com> > On 2009-10-30 19:41, aparna kotha wrote: > > We are trying to compile a .c file using llvm-gcc --emit-llvm . > > > > The produced output has a variable name different from its name in the > > .c file. We have tried it on different llvm-gcc versions and

Török Edwin <edwintorok at gmail.com> writes: > What are we left with then? Only 4.2 and 4.3? On SLES 10.1 at least. I think it is highly platform dependent. > I only use 4.4 since a while, and it works fairly well. On what platform? > Are you sure it is not a bug in the regression tests themselves > (strict-aliasing bugs, etc.)? No, I'm not sure. > Which

On Wed, Mar 26, 2008 at 4:09 AM, Evan Cheng <evan.cheng at apple.com> wrote: > > On Mar 25, 2008, at 12:56 PM, Török Edwin wrote: > > The new package is here: > > http://edwintorok.googlepages.com/sqlite_lemon_llvmtest.tar.gz > > Anything else I should change? > > Looks good. Please commit. Should I speak with Chris about commit access? I made the change

Török Edwin wrote: > Yes, I have uploaded the .tar.gz here: > http://edwintorok.googlepages.com/ClamAV-srcflat.tar.gz > [inputs dir contains some symlink, place ClamAV dir in > llvm/projects/llvm-test/MultiSource/Applications to make > links point to right place] > > Hi, Because llvm bug #1730 got fixed, this testcase can run under with the JIT on x86-64 :). I have

OK I figured out what the problem was - I assume you are trying to compile under Snow Leopard? There is a problem with linking against wxWidgets because the prebuilt binaries for wxWidgets are compiled in 32-bit mode, and the default compilation mode in Snow Leopard is 64 bits. See this article for an explanation: http://wiki.wxwidgets.org/Development:_wxMac#Building_under_10.6_Snow_Leopard

On 2011-02-14 20:58, Török Edwin wrote: > On 2011-02-14 20:39, Talin wrote: >> >> >> On Mon, Feb 14, 2011 at 1:17 AM, Renato Golin <rengolin at systemcall.org >> <mailto:rengolin at systemcall.org>> wrote: >> >> I think this deserves a blog post... >> >> I'd like to wait until I get some feedback - I don't know yet if

On 2011-02-14 20:39, Talin wrote: > > > On Mon, Feb 14, 2011 at 1:17 AM, Renato Golin <rengolin at systemcall.org > <mailto:rengolin at systemcall.org>> wrote: > > I think this deserves a blog post... > > I'd like to wait until I get some feedback - I don't know yet if anyone > is having trouble building or running the thing... Hi Talin,

Hi, We are getting closer. 1. In Makefile, all the references to CFLAGS should be CPPFLAGS instead. 2. filterdiff.sh uses sed -re. This causes a problem on Mac OS X where -E means using extended regular expression, not -r. sed: illegal option -- r usage: sed script [-Ealn] [-i extension] [file ...] sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...] Can this

Hi, Looks like the memory_barrier intrinsic got removed in 3.0 and replaced with fence intrinsics. Could someone who understands this change better than me please update the 3.0 release notes? Also the LangRef still mentions llvm.memory.barrier but this is gone from 3.0. Best regards, --Edwin

Evan Cheng wrote: > Hi Edwin, > Hi Evan, > It works fine for me. Thanks! > > We prefer a flat directory structure. Is it possible for you to > separate it out to sqlite3 and lemon rather than having them as sub- > directories under SQLite? Ok. The new package is here: http://edwintorok.googlepages.com/sqlite_lemon_llvmtest.tar.gz Anything else I should change? >

[I assume you meant to send this to the list as well, not just me.] Begin forwarded message: Date: Wed, 3 Nov 2010 14:43:54 +0000 From: Salomon Brys <salomon.brys at gmail.com> To: Török Edwin <edwintorok at gmail.com> Subject: Re: [LLVMdev] Forcing the Interpreter segfaults I have build LLVM in debug mode. Here are the informations of the segfault : memcpy() at 0x7ffff6f6581e

On Sat, 24 Jul 2010 13:41:42 +0200 Alexandre Colucci <timac at timac.org> wrote: > Hi, > > I am currently studying the possibility to make the transition from > gcc 4.2 to llvm-gcc 4.2 for the projects I am working on. Since you are switching compilers, why not switch to clang instead of llvm-gcc? Best regards, --Edwin

On 2008-11-18 12:22, Johan Cockx wrote: > You're right, thanks. However, now I ran into the next problem. > This seems to be related to the fact that I have a 64-bit machine? > > $ ../../src/llvm-gcc/configure --prefix=/home/johan/llvm > --program-prefix=llvm- --enable-llvm=/home/johan/ > llvm/obj/llvm --enable-languages=c,c++ Use --disable-multilib --Edwin

On 2009-01-23 20:30, Ingo Molnar wrote: > * Török Edwin <edwintorok at gmail.com> wrote: > > >> Having said that, llvm-gcc is not yet able to compile the full Linux >> kernel on its own [for example the boot code, due to asm(".code16gcc")], >> but with LLVM 2.4 it was possible to build "arch=UM", and "arch=X86" (by >> using

2011/10/25 Török Edwin <edwintorok at gmail.com>: > Hi, > > Looks like the memory_barrier intrinsic got removed in 3.0 and replaced with fence intrinsics. > Could someone who understands this change better than me please update the 3.0 release notes? > Also the LangRef still mentions llvm.memory.barrier but this is gone from 3.0. r142994 and r142998 for the relevant changes.

I've filed http://www.llvm.org/bugs/show_bug.cgi?id=1912 for the optimizer bug. Evan On Jan 10, 2008, at 11:28 AM, Evan Cheng wrote: > Hi, > > We are getting closer. > > 1. In Makefile, all the references to CFLAGS should be CPPFLAGS > instead. > 2. filterdiff.sh uses sed -re. This causes a problem on Mac OS X where > -E means using extended regular expression, not