similar to: [LLVMdev] Compiler driver

Le 16 déc. 2009 à 10:54, Mark Muir a écrit : > Hi all, > > I'm developing a custom back-end for an odd-ball architecture (but one that is still describable by LLVMTargetMachine). The toolchain that it will fit into doesn't have a linker as such, so I want to use assembly as the default output. I've got to the point of emitting working custom assembly for very simple C

Hi Mark, Mark Muir <mark.i.r.muir <at> gmail.com> writes: > I want to be able to package this compiler as a cross-compiler > - a single binary to go from C to assembly for that target. It > should define a macro (as shown above) to allow the target to > be identified by source code. I was thinking of doing this > using llvmc to capture the above command-line. Is that

Chris Lattner wrote: > > Hi All, > > There's a new snapshot of llvmgcc4 available here: > > http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz Chris, is there any chance that the new frontend will support dynamic loading of backends? I.e: llvm-g++ -load my_backend.so -march=my_arch a.c ? Thanks, Volodya

Hi everyone, I''m currently investigating re-writing our School CMS application in Rails and the only drawback I can see is there isn''t an ample supply (if any) of WYSIWYG In-browser editors written with a raw Ruby backend. We currently use KTML4 which is written with PHP as a base. I''m interested to hear from anyone who''s integrated a PHP based editor into

Hi, I'm working on bringing up complete coverage for a Gentoo x32 "desktop" system. I've been cooking up quite a few patches for various packages to push upstream, but right now, the biggest blocker is the lack of support for building with/codegen targeting x32 in llvm/clang. Since the x32 patches were sent last year, I see support code has landed in LLVM, and basic handling of

Hi, I have sent this mail to info@puppetlabs.com and received no answer, so I''m posting here as well; I hope somebody at PuppetLabs will be able to help. I have a local mirror of apt.puppetlabs.com which has been broken for at least a few days: the apt/dists/ subdirectory only contains symlinks to non-existent files. [mirror@excellent dists]$ ls -l total 0 lrwxrwxrwx 1 mirror mirror 29

I've been working on ELF object support for the MicroBlaze backend and found that ELFObjectWriter assumes the x86/x86-64 architecture. Attached is a patch that makes the 16-bit e_machine value in the ELF header configurable by the target backend. Right now the target backend simply passes the 16-bit value that it would like to use in the ELF header. I have considered a second approach where

Clang patch for X32 support. Applies against current trunk. --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6 backward compatibility">; def m3dnowa : Flag<["-"], "m3dnowa">,

On Mon, 2004-08-02 at 15:03, Chris Lattner wrote: > > Since there's been little feedback on the design document I sent out, > > some decisions are being made in order to progress the work. If you have > > strong feelings about any of these, voice them now! > > > > 1. Name = llvmcc > > Why not 'llvmc' "llvm compiler"? What does the extra C

Hello, I''ve created a little class which should unpack a 7z archive on Windows. The class has a parameter for passing in the archive version, so that I can trigger an update when a new version of the archive is available. A simplyfied version looks like this (requires 7z): class my_archive ($version = undef) { file { ''version'': path =>

On Mon, Aug 02, 2004 at 07:23:06PM -0500, Chris Lattner wrote: > > > > 1. Name = llvmcc > > > > > > Why not 'llvmc' "llvm compiler"? What does the extra C mean? > > > > I dunno. Perhaps cause Misha liked it. But, you do have a point there. LLVMCC = LLVM Compiler Collection, a la GCC After all, it's going to be the

I checked recent revisions 138624 and 138620 and both produce this log with gcc-4.6.0 on FreeBSD-8.2-STABLE amd64: gmake[2]: Entering directory `/usr/home/yuri/llvm-svn/llvm-objects/lib/CodeGen' llvm[2]: Compiling LLVMTargetMachine.cpp for Release build /usr/home/yuri/llvm-svn/llvm/lib/CodeGen/LLVMTargetMachine.cpp:253:3: error: ‘AsmStreamer’ does not name a type

On 13 Jan 2010, at 16:43, Nick Lewycky wrote: > Mark Muir wrote: >> - Run the existing Clang tool on each source file, using -emit-llvm to generate a .bc file for each module. >> - Run llvm-link to merge them into a single .bc file. >> - Run llc to generate a complete machine assembly. >> >> However, with optimisations enabled, the resulting code is not as

On 13 Jan 2010, at 20:34, Nick Lewycky wrote: > On 13 January 2010 12:05, Mark Muir <mark.i.r.muir at gmail.com> wrote: > > But... now there's a small problem with library calls. Symbols such as 'memset', 'malloc', etc. are being removed by global dead code elimination. They are implemented in one of the bitcode modules that are linked together (implementations

Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's

I'm working on LLDB and we have a bunch of code that is manually manipulating triples and doing a bunch of nasty stuff to account for the fact that llvm::Triple doesn't currently have a way to detect x86_64h. Is this something that llvm::Triple could be modified to support? Either as a new ArchType, or a new SubArchType? -------------- next part -------------- An HTML attachment was

I''d like to announce acts_as_habtm_list plugin for rails. acts_as_habtm_list is a Ruby on Rails plugin, that can manage ordered lists through a join-table. It is providing almost the same Api as acts_as_list. The position column has to be defined in the join table. You can find additional information at: http://www.inlet-media.de/acts_as_habtm_list/ Install it executing this command

Hi Jonathan, This looks a bit odd. Any reason for the unknown->none conflating in this way? For most (all) of the ports unknown-elf works the same as none-elf. I'm also not sure if someone decided to have, arm-codesourcery-elf that this would still work with the patch. Thoughts? -eric On Tue, Jun 24, 2014 at 7:35 AM, Amara Emerson <amara.emerson at gmail.com> wrote: > Hi Jon,

On Mon, 2 Aug 2004, Misha Brukman wrote: > On Mon, Aug 02, 2004 at 07:23:06PM -0500, Chris Lattner wrote: > > > > > 1. Name = llvmcc > > > > > > > > Why not 'llvmc' "llvm compiler"? What does the extra C mean? > > > > > > I dunno. Perhaps cause Misha liked it. But, you do have a point there. > > LLVMCC = LLVM

I'm having a go at writing an LLVM backend for the WDC 65816. The documentation page on writing an LLVM backend<http://llvm.org/docs/WritingAnLLVMBackend.html>gives this example of target registration: extern "C" void LLVMInitializeSparcTargetInfo() { RegisterTarget<Triple::sparc, /*HasJIT=*/false> X(TheSparcTarget, "sparc",