similar to: [LLVMdev] LLVM 1.8 Release Announcement [draft]

LLVM 1.8 is available now! Download it here: http://llvm.org/releases/ Release notes here: http://llvm.org/releases/1.8/docs/ReleaseNotes.html This is a great new release with great new features and lots of refinements (better codegen, faster compiles, bugs fixed). One particularly nice feature of this release is that we're back to a regular 3-month release cycle, allowing users to have

Feedback below.. > <will insert overview blurb here> Big new things: llvm-gcc4, new sparc > backend, Generic vector/SSE/Altivec support, X86 Scalar SSE support, > debugging support, many target-independent codegen improvements, inline asm, > llvm.org/web-reg. > > > Core LLVM IR Improvements: > > * The LLVM IR now has full support for representing

Hi All, Here's the first draft of the release announcement for LLVM 1.9 that I'm working on. I'm sure I've forgotten and overlooked something, if so, please let me know! ----- 8< ------ 8< ----- <notes> Note: LLVM now correctly builds itself and passes all regression tests on Darwin X86 and Darwin PPC. No one has tried other targets to my knowledge. We hit

Hi Everyone, Here are my notes on the LLVM 1.7 release, which will go into the final release announcement. As Tanya mentioned, it has been far too long since the last release, and there have been a lot of CVS commits since Novemeber. :) I went through them all and pulled out some of the major improvements, which I've listed below. I'm certain that I have forgotten some things, so

one more misspelling: in readme.llvm from llvm-gcc4 front-end source directory there is the following line (51): $ ../llvm-gcc4-x.y.source/configure --prefix=`pwd`/../install/ --enable-llvm=$LLVMOBJDIR --enable-languages=c,c++$EXTRALANGS $TARGETOPTIONS the value of the --prefix key ends with slash and it's not right. at least the front-end fails to build under cygwin because one more slash

The vector LLVA extension will not be merged into the 1.6 release branch? It will make me have to merge twice: one for 1.6 and one for vector LLVA. When do you plan to merge the vector LLVA to the main trunk, please? On 26/10/05, Chris Lattner <sabre at nondot.org> wrote: > > Hi All, > > I'm putting together the announcement for the LLVM 1.6 release. Here is > what I

Hi Everyone, I'm happy to say that LLVM has made many leaps and bounds since the last update in November. Because we are bumping the major version number with this release, we're letting the release go for twice as long as our planned release schedule (6 months instead of 3). We are currently half way through the LLVM 2.0 development cycle. So far, many important and invasive changes

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,

LLVM 1.7 is available now! Download it here: http://llvm.org/releases/ Release notes here: http://llvm.org/releases/1.7/docs/ReleaseNotes.html This release is huge! It contains about twice the number of new features as any previous release, and includes some big-ticket items that people have been requesting for a long time. In particular, this release contains a completely rewritten llvm-gcc

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

I just compiled the two attached files in 32-bit mode and ran it. It printed efcdab8967452301. I verified via objdump that the my_bswap function contains the follow assembly which I believe matches the assembly you linked to on godbolt. _my_bswap: 1f70: 55 pushl %ebp 1f71: 89 e5 movl %esp, %ebp 1f73: 8b 55 08 movl 8(%ebp), %edx 1f76: 8b 45 0c movl 12(%ebp), %eax 1f79: 0f c8

> 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

Hi all, As of r141677 I have a failing regression test, see below. This is for LLVM built with clang on a Intel Atom running FreeBSD8.2. Should I file a bug for this? Thanks, Ed. ******************** TEST 'LLVM :: CodeGen/X86/bswap.ll' FAILED ******************** Script: -- /usr/home/emeewis/build/llvm-debug-clang-configure/Debug+Asserts/bin/llc <

After I'm adding to the my path llvm-gcc4-1.8-x86-linux/llvm-bin/ that contains llvm-gcc.exe and llvm-g++.exe I still get the same error message: configure: WARNING: ***** llvm-gcc/llvm-g++ was not found, or does not appear to be configure: WARNING: ***** working. Please make sure you have llvmgcc and llvmg++ in configure: WARNING: ***** your path before configuring LLVM. The runtime

pbx18*CLI> module load codec_g729-ast14-gcc4-glibc-pentium3.so Unable to load module codec_g729-ast14-gcc4-glibc-pentium3.so Command 'module load codec_g729-ast14-gcc4-glibc-pentium3.so ' failed. [Dec 22 15:52:45] WARNING[4491]: loader.c:757 inspect_module: Module 'codec_g729-ast14-gcc4-glibc-pentium3.so' does not provide a license key. [Dec 22 15:52:45] WARNING[4491]:

bswapdi2 for i386 is correct Bits 31:0 of the source are loaded into edx. Bits 63:32 are loaded into eax. Those are each bswapped. The ABI for the return is edx contains bits [63:32] and eax contains [31:0]. This is opposite of how the register were loaded. ~Craig On Sun, Nov 25, 2018 at 10:36 AM Craig Topper <craig.topper at gmail.com> wrote: > bswapsi2 on the x86-64 isn't using

Hi @ll, targetting i386, LLVM/clang generates wrong code for the following functions: unsigned long __bswapsi2 (unsigned long ul) { return (((ul) & 0xff000000ul) >> 3 * 8) | (((ul) & 0x00ff0000ul) >> 8) | (((ul) & 0x0000ff00ul) << 8) | (((ul) & 0x000000fful) << 3 * 8); } unsigned long long __bswapdi2(unsigned long

>> Are you sure there isn't any test coverage? As far as I can tell, the tests from https://reviews.llvm.org/rL133503 are still in the tree. I looked at those, but none of them include the full pattern that decomposes into bswap and rol. I debugged through the X86 bswap.ll test and verified none of those cases make it through MatchBSwapHWord (they get handled in MatchBSwapHWordLow

Hello Everyone. The tarball with llvm-gcc4 built under mingw32 has just been uploaded to http://llvm.org/prereleases/1.8/llvm-gcc4-1.8-x86-mingw32.tar.bz2 Please consider it highly "experimental". -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Developers, As part of PR411, I have made several of the intrinsic functions non- overloaded. While the assembler and bytecode reader are backwards compatible, front-end writers should start using the non-overloaded versions of the intrinsics. The llvm-gcc has already been updated to generate the new intrinsic names. Other front-ends will start seeing warnings about the names of intrinsics that