Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] llvm 2.1 announcement draft"
2007 Sep 27
0
LLVM 2.1 Release!
Hi All,
LLVM 2.1 is done! Download it here: http://llvm.org/releases/ or
view the release notes: http://llvm.org/releases/2.1/docs/
ReleaseNotes.html
The LLVM 2.1 has many improvements, including three new front-ends, a
huge reduction in -O3 compile times, a new (beta) MIPS backend, and
many optimizer/code generator changes that allow LLVM to produce
better code. In addition to new
2007 Sep 27
0
[LLVMdev] FW: Qs about install on mingw32 (Was [llvm-announce] LLVM 2.1 Release!)
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:
2007 Sep 21
0
[LLVMdev] llvm 2.1 announcement draft
On Friday 21 September 2007, Chris Lattner wrote:
> In addition to this, I've checked in the first draft of the release
> notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/
> ReleaseNotes.html).
The release notes mention llvm-gcc 4.2, but the prerelease only included
llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both?
Bye,
Maarten
--------------
2007 Sep 21
1
[LLVMdev] llvm 2.1 announcement draft
>> In addition to this, I've checked in the first draft of the release
>> notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/
>> ReleaseNotes.html).
>
> The release notes mention llvm-gcc 4.2, but the prerelease only included
> llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both?
I will be releasing a source tar ball of llvm-gcc4.2, but
2006 Apr 19
4
[LLVMdev] First draft of release notes done
Please take a look:
http://llvm.org/docs/ReleaseNotes.html
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2006 Aug 08
5
[LLVMdev] llvm 1.8 release notes draft
Hi All,
Here's the first draft of the LLVM 1.8 release notes. Please take a look
and send me any comments or feedback you have:
http://llvm.org/docs/ReleaseNotes.html
Thanks!
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2006 Aug 09
0
[LLVMdev] llvm 1.8 release notes draft
On Aug 8, 2006, at 10:28 AM, Chris Lattner wrote:
>
> Hi All,
>
> Here's the first draft of the LLVM 1.8 release notes. Please take
> a look and send me any comments or feedback you have:
> http://llvm.org/docs/ReleaseNotes.html
>
Trivial changes:
* Most of LLVM is now built with "-pedantic", ensuring better
portability to more C++ Compilers.
Probably
2006 Aug 08
1
[LLVMdev] llvm 1.8 release notes draft
Hello Chris
Tue, 8 Aug 2006 10:28:44 -0700 (PDT) you wrote:
> Here's the first draft of the LLVM 1.8 release notes. Please take a
> look and send me any comments or feedback you have:
> http://llvm.org/docs/ReleaseNotes.html
I think list of platforms should include "Intel and AMD machines
running on Win32 using MinGW libraries (native)". Or something like
this.
--
With
2006 Aug 08
0
[LLVMdev] llvm 1.8 release notes draft
misspellings:
What's new, 1st paragraph: "nightly tester <http://llvm.org/nightlytest/>,
llvm-config enhancEments";
've found nothing wrong except of it :)
On 8/8/06, Chris Lattner <sabre at nondot.org> wrote:
>
>
> Hi All,
>
> Here's the first draft of the LLVM 1.8 release notes. Please take a look
> and send me any comments or feedback you
2006 Apr 20
0
[LLVMdev] First draft of release notes done
> Please take a look:
> http://llvm.org/docs/ReleaseNotes.html
GCC4.0-based llvm-gcc front-end section:
Replace the second "in addition" with something else.
"If you can use it, llvm-gcc4 is offers significant new functionality":
remove is
"In 1.8, it will be removed, replaced with the new SPARC backend."
and replaced (no comma)
"now have initial
2013 May 07
0
[LLVMdev] [cfe-dev] [Announcement] 3.3 Tentative Release Schedule
> We will be branching for the 3.3 release one Monday, May 6th at 5PM PDT (Tuesday, May 7th 12:00 midnight GMT).
I noticed there is a 3.3 branch in svn, but not in git. Anton, are you
still the one managing the git repos?
Also, I just added a note to the release info on trunk before noticing
we had branched. I was about to port it over, but then noticed that
2007 May 14
3
[LLVMdev] llvm 2.0 release announcement [draft]
Hi Everyone,
It is getting to be that time again. I've scoured llvm-commits and
collected a list of some of the major features we've developed since
the last status update (from Feb 21). Please take a look and send me
(off list) additions, feedback, corrections, etc. As usual, if I
missed something, it's probably because there is such a huge amount
of stuff happening,
2008 Feb 02
3
[LLVMdev] Problem Compiling llvm-gcc 4.2
>>
Dear All,
I have been trying for days but still cannot break this barrier. May I
get your help?
I have compiled llvm-2.1 successfully and make install. When I proceed
with llvm-gcc-4.2-2.1, however, I keep getting linking error as
attached. Some functions with totally different content conflict with
each other in linking process.
That is a Linux box (Debian, with 2.6.23-1
2006 Aug 09
2
[LLVMdev] llvm 1.8 release notes draft
Thanks all, I've incorporated all the feedback so far:
http://llvm.org/ChrisLLVM/projects/llvm-www/releases/1.8/docs/ReleaseNotes.html
-Chris
On Tue, 8 Aug 2006, Bil wrote:
> On Aug 8, 2006, at 10:28 AM, Chris Lattner wrote:
>>
>> Hi All,
>>
>> Here's the first draft of the LLVM 1.8 release notes. Please take a look
>> and send me any comments
2008 Oct 14
0
[LLVMdev] llvm 2.4 release notes draft
Hi All,
I am done with my first pass over the release notes, you can see them
in mainline here:
http://llvm.org/docs/ReleaseNotes.html
In addition to the inevitable typos and other things that need to be
cleaned up, there are several todo's for specific people:
1. All: please let me know if there is something missing that I forgot.
2. Daniel, please update the clang section [DANIEL].
3.
2008 Jan 10
3
[LLVMdev] LLVM Build Problems on Itanium
Hi,
I am having some difficulties building llvm on Itanium. My procedure for
building LLVM is:
cd /liberty/llvm.ia64/llvm-2.1
./configure
make ENABLE_OPTIZED=1
cd /liberty/llvm.ia64/obj
/liberty/llvm.ia64/llvm-gcc4.2-2.1.source/configure
--prefix=/liberty/llvm.ia64/install
--enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++
--disable-shared
The build of llvm seems to
2008 Jan 10
0
[LLVMdev] LLVM Build Problems on Itanium
Hi,
I've figured out a little more. #if defined DBX_DEBUGGING_INFO ||
XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however,
neither is defined on Intanium. In gt-dbxout.h type_queue's uses are
unguarded and thus are undefined on Itanium. When I compared llvm-gcc's
gt-dbxout.h with FSF gcc's, I found that type_queue was never used in
FSF gcc's version. Does
2008 Jan 10
2
[LLVMdev] LLVM Build Problems on Itanium
On Jan 10, 2008, at 10:29 AM, Thomas Jablin wrote:
> Hi,
>
> I've figured out a little more. #if defined DBX_DEBUGGING_INFO ||
> XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however,
> neither is defined on Intanium. In gt-dbxout.h type_queue's uses are
> unguarded and thus are undefined on Itanium. When I compared llvm-
> gcc's
> gt-dbxout.h
2015 Aug 05
2
CentOS wiki permission
Hi Akemi, Thank you for granting my request.
I just finished translation : http://wiki.centos
.org/Manuals/ReleaseNotes/CentOS7/Korean
May i change Manuals/ReleaseNotes/CentOS7
<http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7/Korean> translation
part for link to Korean Release note ?
I couldn't make my personal homepage, it says "You are not allowed to edit
this page" :)
2020 Mar 24
6
LLVM 10.0.0 Release
I am pleased to announce that LLVM 10 is now available.
Get it here: https://llvm.org/releases/download.html#10.0.0
This release is the result of the LLVM community's work over the past
six months (up to to e26a78e7085 on master plus commits up to
d32170dbd5b on the release/10.x branch).
Some highlights include:
- C++ Concepts support in Clang
- Clang no longer runs in a separate process