similar to: [LLVMdev] release notes: please mention Intrinsic::memory_barrier removal in 3.0

Do these need to go into the 3.0 branch? -bw On Oct 25, 2011, at 5:59 PM, Eli Friedman wrote: > 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? >>

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.

On Wed, Oct 26, 2011 at 11:36 AM, Bill Wendling <wendling at apple.com> wrote: > Do these need to go into the 3.0 branch? r142994 is necessary; I thought I already sent you an email about that. r142998 only touches the release notes; it looks like you're hacking on those on trunk. -Eli > On Oct 25, 2011, at 5:59 PM, Eli Friedman wrote: > >> 2011/10/25 Török Edwin

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

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

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

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

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

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

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,

2009/6/15 Török Edwin <edwintorok at gmail.com>: > Write some C++ code into llvm.org/demo, and watch the output assembly, That shows how to use the c++ runtime for handling c++ style exceptions. More useful might be an llvm implementation of __cxa_throw, which I could then modify. ;)

Hi All, I was looking into using LLVM with C++. Currently there is almost no C++ support (C support only). Just wondering who is the person to contact so I could help out with C++ extension for LLVM. With Best Regards KaZ Department of Mathematics and Computing Imperial College London

On Thu, 09 Dec 2010 11:24:19 -0600 greened at obbligato.org (David A. Greene) wrote: > greened at obbligato.org (David A. Greene) writes: > > > Often I run a few different builds in parallel, with different > > obj/build directories. Is it possible that the test infrastructure > > writes something to the source directories or some common temp > > directory? That

On 2009-01-30 18:19, Kasra wrote: > Hi All, > > I was looking into using LLVM with C++. Currently there is almost no C++ support (C support only). > LLVM is written in C++, has a C++ API, and llvm-gcc frontend can compile C++ programs. What exactly is the C++ support you are missing? Best regards, --Edwin

Hi, What is the status of building LLVM trunk with Visual Studio 2010 (32/64-bit)? Were the build problems of LLVM 2.7 fixed? Best regards, --Edwin

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