similar to: [LLVMdev] Please update LDC references on LLVM website

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

On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? Hi Rafael, the patch is attached. @Mikael, Tim Thanks for the help. I really needed only the link to the repo. Regards, Kai > > 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

You need to get the LLVM Sphinx docs using SVN or Git. If you want it, I can do the changes for you since I have already everything in place. -- Mikael 2013/12/3 Kai Nacke <kai at redstar.de> > 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,

Hi all, I'm currently working on getting our (LDC) compiler to run on Win32/MinGW, now that DW2-style EH is available for it. The D programming language has a feature equivalent to LLVM module level inline assembly, so we need to at least partly follow the x86 D calling convention (http://dlang.org/abi.html). Most notably, the ABI mandates that the callee cleans the stack. On the various

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

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

hi LLVM community, Maybe it is the wrong place, sorry LDC it is a D compiler D1 : http://www.dsource.org/projects/ldc D2 : http://bitbucket.org/prokhin_alexey/ldc2 We need some LLVM developper for help this project, they are an ric channel on freenode #ldc Any help are welcome Thanks for all Yours sincerely, -- jonathan MERCIER <bioinfornatics at gmail.com>

Hey Chris et al., >> 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. . . >Wow, very very nice! Have you pointed this out to the other D users? >-Chris Yes, I have let

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

Maybe it's time to add it to the LLVM projects list. :) The original annoucement on digitalmars.D.announce and http://www.incasoftware.de/~kamm/projects/index.php/2009/01/09/ldc-09-released/ was: --- The first version of LDC (http://www.dsource.org/projects/ldc), the LLVM based compiler for version one of the D programming language has been released for x86-32 Linux. Get it here:

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

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

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

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 number. This requires the user to keep the llvm source tree

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

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 :-) -- _,-=._ /|_/| `-.} `=._,.-=-._., @ @._, `._ _,-.

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

Hi Russel, I never tried to build LLVM with nmake. With msbuild it works without problems. You can find a short desription here: http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC, section Build LLVM. Regards Kai On 24.08.2013 21:15, Russell Wallace wrote: > I'm trying to build LLVM 3.3 using cmake/nmake, Microsoft C++ 2012, on a > 64-bit Windows 7 system. I

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