similar to: [LLVMdev] External projects that work with LLVM 2.5

If your project works with LLVM 2.7 and you want it included in the release notes, please email me a blurb to include ASAP. -Chris

Hi Everyone, LLVM 2.5 is live: you can download it here: http://llvm.org/releases/ and read about it here: http://llvm.org/releases/2.5/docs/ReleaseNotes.html LLVM 2.5 includes an amazing collection of bug fixes, performance improvements (both in the compiler itself and in the generated code) and new features. Some highlights include a new XCore backend, significantly improved llvm-gcc

Hi All, I'm preparing the release notes for LLVM 2.8 and would appreciate it if you could send me a blurb if you maintain an out-of-tree project that works with it. The list from 2.7 was here: http://llvm.org/releases/2.7/docs/ReleaseNotes.html#externalproj I need your input by saturday night (Oct 2). No projects listed in 2.7 will be carried forward unless you send me an update. Thanks

Dear Chris, Project Name: Kai Project Website: http://www.oriontransfer.co.nz/research/kai Project Description: Kai (Japanese 会 for meeting/gathering) is an experimental interpreter that provides a highly extensible runtime environment and explicit control over the compilation process. Programs are defined using nested symbolic expressions, which are all parsed into first-class values with

The idea of adding an “incubation” stage to projects in the LLVM world seems to be positively received. I also noticed that we don’t really document the new project policy in general in the LLVM Developer Policy. To help with both of these Stella and I worked together to draft up a new section for the LLVM developer policy (incorporating the existing “New Targets” section). Ahead of proposing a

What is the procedure for updating the release notes? I've been committing changes to the trunk version, should I be editing them elsewhere? Or will the trunk version be merged in? On Mon, Dec 3, 2012 at 4:12 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hi, > > > Are we going to have a mingw release this time? > > As far as I know there is no change from 3.1

Are we going to have a mingw release this time? On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hello, > > - State of the 3.2 release > > Release is progressing as scheduled, RC2 has > been created and is being tested. RC2 sources > and binaries can be downloaded from: > > http://llvm.org/pre-releases/3.2/rc2/ > > > -

Hi LLVM Friends, Fans, Followers and Fanatics, LLVM 2.6 is live! You can download it here: http://llvm.org/releases/ and read about it here: http://llvm.org/releases/2.6/docs/ReleaseNotes.html This release includes approximately 6 months of development that provide major enhancements and new features over the LLVM 2.5 release. This includes significantly better X86-64 code generation,

Alright, can you please pull in r169280? On Tue, Dec 4, 2012 at 12:56 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > On 12/4/2012 10:14 AM, Justin Holewinski wrote: > > What is the procedure for updating the release notes? I've been > committing > > changes to the trunk version, should I be editing them elsewhere? Or > will > > the trunk version be

Hi, > Are we going to have a mingw release this time? As far as I know there is no change from 3.1 and Mignw is considered experimental. Incidentally RC2 mingw32 binaries have been uploaded and are available for download and testing. http://llvm.org/pre-releases/3.2/rc2/clang+llvm-3.2rc2-i386-mingw32-EXPERIMENTAL.tar.gz Pawel > > > On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro

On Oct 11, 2011, at 2:33 PM, Chris Lattner wrote: > > On Oct 11, 2011, at 1:24 PM, Daniel Dunbar wrote: > >> Hi all, >> >> I would like to deprecate the LLVM project's "official" support of >> setting up the Makefiles / autoconf configurations in such a way that >> external projects are encouraged to leverage them in their own build. >

Hello, - State of the 3.2 release Release is progressing as scheduled, RC2 has been created and is being tested. RC2 sources and binaries can be downloaded from: http://llvm.org/pre-releases/3.2/rc2/ - Release notes and documentation With RC2 the 3.2 release has reached the point where it is feature complete and we can turn the attention to updating documentation, especially the release

On 12/4/2012 10:14 AM, Justin Holewinski wrote: > What is the procedure for updating the release notes? I've been committing > changes to the trunk version, should I be editing them elsewhere? Or will > the trunk version be merged in? The exact procedure is not spelled out but I think the easiest would be to merge relevant "ReleaseNotes.html" changes from the trunk,

hi Nathan, > > This has been working for about two months and I can't readily figure > out what I changed to break it. > have you recently upgraded from version 2.5 to 2.6? maybe it's related to my bugzilla PR 3666. tobias

Hey, Do you want projects which specifically use LLVM 3.1 or just LLVM in general? Regards, Alex On Fri, May 11, 2012 at 10:55 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. > > Also, if you have a project which uses LLVM, please

OK, so I pulled down the two MinGW32 binaries. I bzip2 -d the two into .tar files, then tar xvf them into my directory of choice. (C:/Prg/llvm-2.1 in this case.) When I run the compiler over hello.c, as per the Getting Started Guide, compilation works for both native and LLVM BC. When I run the native hello.exe, it works. When I try to run lli hello.bc, I get an unsatisfied DLL link error:

On Aug 25, 2009, at 11:34 PM, Albert Graef wrote: > Chris Lattner wrote: >> Given that we don't guarantee backwards compatibility and prefer to >> keep >> our APIs clean and tidy, why should we take this? > > I already said that: To make it easier for out-of-tree frontends to > support at least the last few LLVM versions. If that's a low priority > then

On 11.05.2012, at 22:55, Bill Wendling wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. I added some bigger picture notes to http://llvm.org/docs/ReleaseNotes.html this morning, but we're still missing a lot of text, specifically: - clang: clang has it's own release notes

On Jan 17, 2009, at 1:25 PM, Albert Graef wrote: > Chris Lattner wrote: >> In the end, I consider this to be a yet-another chapter in the >> "functional language people don't like LLVM" saga. > > Yet another counterexample: > > http://pure-lang.googlecode.com/ Hey, this is incredibly cool. I had never heard of pure, nice work! Would you mind writing a

> On Nov 7, 2019, at 5:54 PM, Daniel Sanders via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > -1 to "squash and merge" being the only option if rebase+push (--ff-only) is possible. I'd rather we use our judgement to decide what's appropriate for the pull request at hand rather than have a blanket rule. > > Personally, if I have multiple commits