similar to: [LLVMdev] First Pass at building dragon egg-3.3 for clang 3.3 - using gcc-4.7

LLVM Friends, First time attempting a build of dragonegg, using our shiny new install of clang-3.3. I'm clearly off to a terrifying start! dragonegg-3.3.src$ CXX=/usr/bin/gcc GCC=/usr/bin/gcc ENABLE_LLVM_PLUGINS=1 LLVM_CONFIG=/usr/bin/llvm-config CFLAGS=-I/usr/clang/3.3/lib/clang/3.3/include CXXFLAGS="-I/usr/clang/3.3/lib/clang/3.3/include" make Compiling

Duncan, Yes, I'd been pretty much performing the same diagnosis in parallel - it seems we just don't have that libLLVMSupport library built. Last night, tried the build of clang a few different ways to get that library built - including specifying the --gcc-toolchain option. No Joy! Which of the clang/llvm source trees provides it? or is it in another source package? tools? Is there a

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

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

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

On Fri, Dec 07, 2012 at 06:57:36PM +0100, Duncan Sands wrote: > 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. > Duncan, I have opened

Hi, I'm trying to compile release 3.2 of DragonEgg (checked out from http://llvm.org/svn/llvm-project/dragonegg/branches/release_32. I'm at revision 170458), under Ubuntu (Ubuntu 12.04.1 LTS (GNU/Linux 2.6.39-gcg-20121018 x86_64)) and I get the following error. tmroeder at myubuntu:~/src/dragonegg$ make Compiling utils/TargetInfo.cpp Linking TargetInfo Compiling Aliasing.cpp

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

That did it, thanks for the help! For the future is there a set of documentation for these bindings, or their equivalent c functions? I tried looking but was having trouble finding anything that seemed to match. On Wed, Jun 29, 2016 at 1:35 AM Andrew Wilkins <axwalk at gmail.com> wrote: > On Wed, 29 Jun 2016 at 00:32 Brian Picciano via llvm-dev < > llvm-dev at lists.llvm.org>

Michael, I'm looking at flushing out the mach-o driver and targetinfo. Can we rename the "ld64" flavor to "darwin". The command line tool on MacOSX is called "ld" - just like on unix. The name ld64 is the current source repository name for the linker. Once lld takes over, the term ld64 won't mean anything. I've worked through adding DarwinOpts.td

I was wandering how much is the overhead of virtual function calls of TargetInfo member functions. TargetInfo handles platform-specific details, and we have target-specific subclasses of that class. The subclasses override functions defined in TargetInfo. The TargetInfo member functions are called multiple times for each relocation. So the cost of virtual function calls may be non-neglible. That

> On Mar 30, 2016, at 4:25 PM, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Wed, Mar 30, 2016 at 4:20 PM, Sean Silva <chisophugis at gmail.com <mailto:chisophugis at gmail.com>> wrote: > I believe the relocation stuff that Rafael is currently working on will make this a non-issue (it will make relocation application much friendlier for the CPU).

I believe the relocation stuff that Rafael is currently working on will make this a non-issue (it will make relocation application much friendlier for the CPU). However, even in the current scheme, since the target is fixed, all the indirect call sites should be monomorphic and so there shouldn't be much branch-prediction cost (certainly nothing that would cause 1.8% performance delta for the

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?

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... GCC=/sw/lib/gcc4.5/bin/gcc-4 LLVM_CONFIG=/sw/bin/llvm-config make CPPFLAGS="-DENABLE_LTO -I/sw/include" Compiling utils/TargetInfo.cpp <command-line>: warning: "__STDC_LIMIT_MACROS"

On Wed, Mar 30, 2016 at 4:20 PM, Sean Silva <chisophugis at gmail.com> wrote: > I believe the relocation stuff that Rafael is currently working on will > make this a non-issue (it will make relocation application much friendlier > for the CPU). > I don't think Rafael's patch would make this a non-issue. He's making scanRelocs to create data, which would reduce the

On Fri, Apr 08, 2011 at 07:37:39AM -0400, Jack Howarth wrote: > 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...

On Wed, Mar 30, 2016 at 4:25 PM, Rui Ueyama <ruiu at google.com> wrote: > On Wed, Mar 30, 2016 at 4:20 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> I believe the relocation stuff that Rafael is currently working on will >> make this a non-issue (it will make relocation application much friendlier >> for the CPU). >> > > I don't think