similar to: [LLVMdev] [PATCH] llvm-config: add svn revision to --version

Benjamin Kramer wrote: > At the moment llvm-config outputs "2.6svn" if llvm is build from trunk > > $ llvm-config --version > 2.6svn > > Some external projects (built out-of-tree) need to know which revision > of llvm is installed. LDC currently asks llvm-config --src-root for the > source directory and then parses svn info's output to get the revision

Frits van Bommel skrev: > Benjamin Kramer wrote: > >> At the moment llvm-config outputs "2.6svn" if llvm is build from trunk >> >> $ llvm-config --version >> 2.6svn >> >> Some external projects (built out-of-tree) need to know which revision >> of llvm is installed. LDC currently asks llvm-config --src-root for the >> source

Xerxes Rånby wrote: > Frits van Bommel skrev: >> Benjamin Kramer wrote: >>> The attached patch modifies the llvm build system (both autotools and >>> cmake) to write the revision into PACKAGE_VERSION: >>> >>> $ llvm-config --version >>> 2.6-71981 >>> >> I don't think that's enough for LDC; we want to be able to

On 2009-05-18 20:06, Frits van Bommel wrote: > Xerxes Rånby wrote: > >> Frits van Bommel skrev: >> >>> Benjamin Kramer wrote: >>> >>>> The attached patch modifies the llvm build system (both autotools and >>>> cmake) to write the revision into PACKAGE_VERSION: >>>> >>>> $ llvm-config --version

Can you send a patch? On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: > Hi! > > I like to submit some updates to the LLVM website regarding the LDC > compiler. All links are currently out-of-date. The following pages need > updates: > > On page http://www.llvm.org/Users.html, please replace the existing entry > "LLVM D Compiler" in section

Hi! I like to submit some updates to the LLVM website regarding the LDC compiler. All links are currently out-of-date. The following pages need updates: On page http://www.llvm.org/Users.html, please replace the existing entry "LLVM D Compiler" in section "Open Source Projects" with: <tr> <td><a href="http://wiki.dlang.org/LDC/">

Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

Hi Rafael, is there a repository with the static pages or should I simply produce a diff between the 2 versions? Regards, Kai On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? > > On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: >> Hi! >> >> I like to submit some updates to the LLVM website regarding the LDC >> compiler.

Benjamin Kramer <benny.kra at googlemail.com> writes: > In the current version of my patch the revision is only updated on a > re-configure/CMake. On a second thought that is quite stupid. But I'm > not sure what's the best way to fix this. I guess we need to add a > target which is always run to llvm-config's Makefile ... This is easy: see the logic for

Hello everyone, I just thought I would let people here know that ldc (llvm backend for the D Programming Language) is getting pretty usable (a few larger libraries compile) and it now has x86-64 support added. I decided to run some timings on some D and C++ code to compare ldc to dmd (the mainline compiler), gdc (the gcc based D compiler) and g++. I used a ray tracing program found in this

Hello, While trying to find out why the LDC compiler refuses to generate object code for MSP430 targets (but generates MSP430 assembly or LLVM IR/bitcode), I came across the following apparent inconsistency. This works: $ clang --target=msp430 -c test.c This doesn't work: $ clang --target=msp430 -S -emit-llvm test.c $ llc -filetype=obj test.ll /opt/msp430/bin/llc: target does not support

On Oct 27, 2008, at 11:03 PM, Kelly W wrote: > Hello everyone, > > I just thought I would let people here know that ldc (llvm backend > for the D Programming Language) is getting pretty usable (a few > larger libraries compile) and it now has x86-64 support added. I > decided to run some timings on some D and C++ code to compare ldc to > dmd (the mainline compiler),

On Thu, Jul 6, 2017 at 2:19 AM, Tim Northover <t.p.northover at gmail.com> wrote: > On 5 July 2017 at 17:51, Luís Marques via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Cool. When I did that on macOS, LDC generated a lot of complaints, > possibly > > because it is assuming mach-o files. I tried changing from > -mtriple=msp430 > > to

On Thu, Jul 6, 2017 at 1:35 AM, Nicholas Wilson < iamthewilsonator at hotmail.com> wrote: > Luís, try using the -no-integrated-as flag to execute the assembler for > you. > We should probably make that the default for MSP430. > Cool. When I did that on macOS, LDC generated a lot of complaints, possibly because it is assuming mach-o files. I tried changing from -mtriple=msp430

Hi all, updated py-htbstat: http://www2.ldc.net/~dor/py-htbstat/ Some screenshots: http://www2.ldc.net/~dor/py-htbstat/shots/shots.html It''s now possible to use classids in form ''xxxx:xxxx'' now (actually i dont know why i''ve made it to use ''1:xxxx'' only :-) -- _,-=._ /|_/| `-.} `=._,.-=-._., @ @._, `._ _,-.

Hi all, As part of my compute work I'm trying to get some TGSI compute code to work. The code from mesa/src/gallium/tests/trivial.c works. So now I'm trying to get a "native" tgsi kernel to run via clover, I'm using Francisco's nbody.c example for this: https://fedorapeople.org/~jwrdegoede/nbody.c Which does not work, at first I thought there was an issue with the

Hi, I'm considering giving the Grandstream BudgeTone-102 phones a try. I've been using Cisco 7960's to date, but the low cost of the Grandstream phones are hard to ignore. I have two questions: 1) Does the message waiting indicator on the BudgeTone's work with Asterisk? 2) The one line 12-digit LDC concerns me a bit. Is the LCD able to display both the CID number and name on

Hello all, For CI testing of LDC with LLVM trunk we use CircleCI, which offers Ubuntu Trusty 14.04. We use apt.llvm.org, but the latest update of the "nightly" package is now more than a month ago. Previously the update rate was once a week, which was OK as it meant that we only had a few days of test breakage after an API change (and after a dev updated LDC to build with a locally

Hi all, I am writing a custom backend. Doing more testing i notice that for some reason something like: int test(int x) { return x - 1; } is being turned into this IR: ; Function Attrs: nounwind define i32 @test(i32 %n) #0 { entry: %n.addr = alloca i32, align 4 store i32 %n, i32* %n.addr, align 4 %0 = load i32* %n.addr, align 4 %sub = sub nsw i32 %0, 1 ret i32 %sub } But finally in

Also, where's the exit op? Perhaps what's happening is that you don't have an exit and it just goes off executing into the ether? On Tue, Dec 15, 2015 at 12:00 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > A few things that stand out: > > 0: ld u32 %r219 c0[0x0000000000000000+0x0] (0) > > wtf is that 0x0000000000000 thing doing there? Was it a %rX which got