similar to: [LLVMdev] Can't compile Dragonegg

Hi Tom, DragonEgg depends on GCC's and LLVM's internal headers, auto-host.h is one of them. Try to add GCC and LLVM_CONFIG with your make command as described here http://dragonegg.llvm.org/ in section "Getting it". Best, - Dima. On 12/18/2012 10:24 PM, Tom Roeder wrote: > Hi, > > I'm trying to compile release 3.2 of DragonEgg (checked out from >

Hi, I suggest add the id attribute for each <h2> tag in www/index.html. Thus we can refer to the "Getting it" section in the dragonegg homepage page (the only web page) by simply the given URL: http://dragonegg.llvm.org#GettingIt Regards. On Wed, Dec 19, 2012 at 6:32 AM, Dmitry Mikushin <dmitry at kernelgen.org>wrote: > Hi Tom, > > DragonEgg depends on GCC's

Hi Mingliang LIU, > I suggest add the id attribute for each <h2> tag in www/index.html. Thus we can > refer to the "Getting it" section in the dragonegg homepage page (the only web > page) by simply the given URL: > http://dragonegg.llvm.org#GettingIt this already works: http://dragonegg.llvm.org/#gettingrelease But maybe could be done better or more consistently?

On Sat, Feb 15, 2014 at 7:08 PM, Eric Christopher <echristo at gmail.com> wrote: > On Tue, Feb 11, 2014 at 9:46 AM, Tom Roeder <tmroeder at google.com> wrote: >> On Tue, Feb 11, 2014 at 9:12 AM, Reid Kleckner <rnk at google.com> wrote: >>> On Tue, Feb 11, 2014 at 12:28 AM, Richard Osborne <richard at xmos.com> wrote: >>>> >>>>

On Thu, Mar 20, 2014 at 3:29 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Mar 17, 2014 at 10:28:52AM -0700, Tom Roeder wrote: > > On Tue, Feb 25, 2014 at 5:41 PM, Eric Christopher <echristo at gmail.com>wrote: > > > > > On Mon, Feb 24, 2014 at 4:33 PM, Tom Roeder <tmroeder at google.com> wrote: > > > > > > > >

On Tue, Feb 25, 2014 at 5:41 PM, Eric Christopher <echristo at gmail.com>wrote: > On Mon, Feb 24, 2014 at 4:33 PM, Tom Roeder <tmroeder at google.com> wrote: > > > > I'm definitely interested in removing the inline asm bits. I'm not > > sure what you mean by a pseudo-plt, though; do you mean hooking into > > the code that generates the Procedure

> The way I've implemented it (see the patch I sent to llvm-commits > yesterday), it's not just metadata: the intrinsic lowers to the > jumptable entry code given above. The CFI pass then generates a > function for each jump table; the function consists solely of these > intrinsic calls. Well, the intrinsic you proposed has no effect on the caller and has non-local effects

Hi, In my work applying -flto to Chrome, I need to set some names to be skipped by the InternalizePass; otherwise, the linking stage fails (i.e., when building the chrome binary). In the past, I had a tiny patch that I hadn't submitted to LLVM: it was something like: Index: Internalize.cpp =================================================================== --- Internalize.cpp (revision

On Tue, Feb 11, 2014 at 9:12 AM, Reid Kleckner <rnk at google.com> wrote: > On Tue, Feb 11, 2014 at 12:28 AM, Richard Osborne <richard at xmos.com> wrote: >> >> >> On 11 Feb 2014, at 08:15, Eric Christopher <echristo at gmail.com> wrote: >> >> > On Mon, Feb 10, 2014 at 11:51 PM, Reid Kleckner <rnk at google.com> wrote: >> >>

Hi all, I wanted to have a look at wxRuby on a recent version of ruby 1.9 (ruby-1.9.1-preview1) on Ubuntu 8.10 x86. Here is the result : chauk-mean at MyUbuntu:~/wxruby2$ ruby19 -v ruby 1.9.1 (2008-10-28 revision 19983) [i686-linux] chauk-mean at MyUbuntu:~/wxruby2$ rake19 WXRUBY_VERSION=1.9.9 gem (in /home/chauk-mean/wxruby2) Enabling DYNAMIC build Enabling RELEASE build Enabling UNICODE build

On Fri, Apr 08, 2011 at 08:28:27AM +0200, Duncan Sands wrote: > Hi Jack, > > > The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn > > (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the > > build fails as... > > what does the command > ./TargetInfo -p > return (the TargetInfo program

Thanks for the followup. If I understand the suggestion correctly, this doesn't solve the problem of building a jump table to call into other functions, since, as you note, indirectbr can only call into blocks in the same function. Is the conclusion then that there is no way to do this in LLVM IR? It looks like these kind of restrictions (no branching between functions and no instructions

Anton, please add release_32 also in; clang-tools-extra compiler-rt dragonegg libcxxabi lldb They have release_32 in svn. I don't know they might be released, though. And, could you suppress generating refs/heads/svn-tags and prune them for now? I am sure that orphan branches will stress the llvm.org server to begin git-pack-ing whole tree. ...Takumi 2012/11/15 Anton Korobeynikov

Duncan, I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the compiler errors... GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config VERBOSE=1 ENABLE_LLVM_PLUGINS=1 make CPPFLAGS="-g -DENABLE_LTO -I/sw/include" /sw/lib/gcc4.7/bin/gcc-4 --version > /dev/null /sw/opt/llvm-3.2/bin/llvm-config --version > /dev/null Compiling utils/TargetInfo.cpp

On Fri, Dec 07, 2012 at 06:20:37PM +0100, Duncan Sands wrote: > Hi Jack, this occurs because you compiled LLVM with clang (right?) and > dragonegg is compiled with the same flags used to compile LLVM (it is > an llvm-config bug in my opinion that llvm-config output includes these > kinds of optional flags). Duncan, Yes. I believe both fink and MacPorts now default to the clang

Should be there On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Anton, please add release_32 also in; > > clang-tools-extra > compiler-rt > dragonegg > libcxxabi > lldb > > They have release_32 in svn. I don't know they might be released, though. > > And, could you suppress generating refs/heads/svn-tags and prune them

> Is there anything I can do to make the build more verbose so I can debug this? make VERBOSE=1

Hi Jack, this occurs because you compiled LLVM with clang (right?) and dragonegg is compiled with the same flags used to compile LLVM (it is an llvm-config bug in my opinion that llvm-config output includes these kinds of optional flags). Ciao, Duncan. On 07/12/12 18:11, Jack Howarth wrote: > Duncan, > I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the > compiler

Hi Jack, can you please open a bug report asking that llvm-config only provide the minimum set of flags needed to compile code that interfaces with LLVM, rather than (as now) all kinds of unneeded flags such as -g and warnings. Thanks, Duncan. On 07/12/12 18:55, Jack Howarth wrote: > On Fri, Dec 07, 2012 at 06:20:37PM +0100, Duncan Sands wrote: >> Hi Jack, this occurs because you

Duncan, Many thanks for your comments. The core issue we're running into is this: $ GCC=/usr/bin/gcc LLVM_CONFIG=/usr/bin/llvm-config make Compiling utils/TargetInfo.cpp Linking TargetInfo ld: fatal: library -lLLVMSupport: not found ld: fatal: file processing errors. No output written to TargetInfo collect2: error: ld returned 1 exit statusAll other gyrations are attempts to shoehorn