similar to: [LLVMdev] 2.4 Pre-release (v2)

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] 2.4 Pre-release (v2)"

2008 Nov 02
0
[LLVMdev] 2.4 Pre-release (v2)
Tanya M. Lattner dixit: >LLVMers, > >The 2.4 pre-release (v2) is available for testing: >http://llvm.org/prereleases/2.4/ Is it correct that there is no matching clang distfile? A checkout of clang r58548 does not build with the prerelease, seems to require a newer version of llvm-current. (But then, maybe it’d be best anyway if I port llvm-current to MirBSD, because it’ll be easier
2008 Nov 02
2
[LLVMdev] clang (was Re: 2.4 Pre-release (v2))
Dixi quod… >A checkout of clang r58548 does not build with the prerelease, >seems to require a newer version of llvm-current. However, clang r58565 does not build with llvm r58565 either: llvm[4]: Compiling BasicConstraintManager.cpp for Release-Asserts build mpcxx -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/include -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis
2008 Nov 03
2
[LLVMdev] clang
Anton Korobeynikov dixit: >> Any suggestions? >Please do read http://clang.llvm.org/get_started.html about correct >way of building clang. Oh, I did. I took LLVM and Clang from the very same SVN revision even, placed clang in llvm/tools/ and built. This has worked on GNU/Linux for me once, but clang-current seems to rely on things not yet in llvm. Like I said, I’m using r58565 for
2008 Nov 02
3
[LLVMdev] Porting llvm-gcc-4.2
Hello, how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e. MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/ and patch quite some configure scripts, but seeing that llvm-gcc uses LLVM for target specific stuff, how much of this still applies? cpp defines and startup files at the least, probably, for the com- piler driver… Which dependencies does llvm-gcc-4.2 have,
2008 Nov 03
0
[LLVMdev] Porting llvm-gcc-4.2
llvm-gcc bits are but a small part of it. You need to add a new target to llvm. Please read llvm documentation and llvmdev archieve for more information. Evan On Nov 2, 2008, at 7:38 AM, Thorsten Glaser wrote: > Hello, > > how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e. > MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/ > and patch quite
2008 Nov 28
2
[LLVMdev] Disable optimization
Wouldn't Clang be a good option to generating unoptimized LLVM IR? Dan On Nov 28, 2008, at 6:13 AM, Duncan Sands wrote: >> It matters if the optimisations the students have to implement are >> the >> optimisations done implicitly by LLVM. > > They are not really done by LLVM, because no optimizations are done > on the > LLVM IR. They are done by llvm-gcc,
2008 Nov 05
0
[LLVMdev] 2.4 Pre-release (v2)
Hi, I've just tried out version 2.4, and it doesn't work for me in situations where 2.3 seems fine. The current trunk code appears to have the same problem. When I compile a simple program in llvm-gcc, I get a .bc file as output as expected. When running lli or llc on this file, however, I get various errors and an assert, stopping the .s file from being created. Example output of llc:
2008 Nov 17
2
[LLVMdev] OpenBSD Build Failure - 2.4 release
Hi, On Mon, Nov 17, 2008 at 8:32 AM, Edd Barrett <vext01 at gmail.com> wrote: > On Sat, Nov 15, 2008 at 11:19 PM, Daniel Berlin <dberlin at dberlin.org> wrote: >> 3.3 has been unsupported since late 2005 .... > > Its still the default compiler for OpenBSD, although 4.x is available > as a third party package. I will try this. Build works with gcc-4.2. Some
2008 Dec 01
0
[LLVMdev] Disable optimization
Daniel M Gessel dixit: >Wouldn't Clang be a good option to generating unoptimized LLVM IR? More like broken ;-) sometimes at least. >On Nov 28, 2008, at 6:13 AM, Duncan Sands wrote: >> They are not really done by LLVM, because no optimizations are done >> on the >> LLVM IR. They are done by llvm-gcc, a front-end to LLVM: llvm-pcc, anyone? :þ //mirabilos --
2008 Nov 02
0
[LLVMdev] clang (was Re: 2.4 Pre-release (v2))
Hello, Thorsten >>A checkout of clang r58548 does not build with the prerelease, >>seems to require a newer version of llvm-current. That's correct. > Any suggestions? Please do read http://clang.llvm.org/get_started.html about correct way of building clang. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
2008 Nov 11
0
[LLVMdev] Question about SPARC target status
On Nov 11, 2008, at 10:48 AM, Luke K. Dalessandro wrote: > On Tue, 11 Nov 2008, Peter Shugalev wrote: > >> Hi, >> >> Anton Korobeynikov wrote: >>>> I thought llvm-gcc isn't meant to compile for specific target (at >>>> least >>>> with -emit-llvm flag I'm using). >>> No, it is not. C language is highly target-specific,
2020 Jul 15
2
Support for macOS feth devices
On Wed, 15 Jul 2020, Peter Stuge wrote: > is GPL-licensed, so a derivative of that can't be integrated into OpenSSH. A derivative of it, that exposes a general API to do tap-device-like things using stdio and command line options, could be called over its general API from OpenSSH though. Even be developed separately (this would, in fact, even help). bye, //mirabilos -- ?MyISAM tables
2008 Nov 11
3
[LLVMdev] llvm-gcc fails to build libgcc when built with itself
Hello, I’m trying the following thing: • build and install llvm with mgcc (system compiler) • build and install llvm-gcc with mgcc • build llvm with llvm-gcc • deinstall llvm(old), install llvm(new) • build llvm-gcc with llvm-gcc(old) • deinstall llvm-gcc(old), install llvm-gcc(new) However, I have the problem that the llvm-gcc(new) does not work: after it is compiled, it tries to build libgcc2
2008 Nov 12
0
[LLVMdev] llvm-gcc fails to build libgcc when built with itself
Can you bootstrap llvm-gcc (configure with --enable-bootstrap)? Ciao, Duncan.
2008 Nov 11
2
[LLVMdev] Question about SPARC target status
On Tue, 11 Nov 2008, Peter Shugalev wrote: > Hi, > > Anton Korobeynikov wrote: >>> I thought llvm-gcc isn't meant to compile for specific target (at least >>> with -emit-llvm flag I'm using). >> No, it is not. C language is highly target-specific, thus LLVM IR >> obtained from such sources also has the same nice 'property' > > I can see
2008 Nov 05
2
[LLVMdev] 2.4 Pre-release (v2)
Hi, Ben > Hi, I've just tried out version 2.4, and it doesn't work for me in > situations where 2.3 seems fine. The current trunk code appears to have > the same problem. > Value still in symbol table! Type = 'i32' Name = 'tmp3.3' It seems, that you're using gcc, which is known to be broken http://llvm.org/docs/GettingStarted.html#brokengcc -- With best
2008 Nov 09
0
[LLVMdev] clang
Dixi quod… >Like I said, I’m using r58565 for both llvm and clang (now). Must have been broken, as r58935 for both works. I’ve even fixed some system headers for clang now, and mksh – http://mirbsd.de/mksh – builds fine and passes the regression tests (with the Xcode version, about 83% of it failed, back then). Now up to llvm-gcc *sigh*… //mirabilos -- Sometimes they [people] care too
2020 Oct 30
3
SSH client and bracketed paste mode
Hello list, Using a terminal with bracketed paste mode (see [0], [1]), I am not able to paste text while being in the "~C" command line mode. The reason for that is, that while being in that special mode, openssh-client attempts to interpret the special bracketed paste start escape sequence, which does not work: root at localhost:~# ssh> ^[[200~-L
2010 Aug 18
2
[LLVMdev] Using ValueSymbolTable...
Hi all, I have a question regarding populating ValueSymbolTable of a Function. Is it that ValueSymbolTable is populated automatically whenever an alloca instruction is created using IRBuilder or do we need to explicitly populate?? If we need to populate explicitly, the insert method in ValueSymbolTable is private, so how can we do it? Currently, I am trying to access the symbol table as below:
2007 May 17
8
[LLVMdev] Antw.: 2.0 Pre-release tarballs online
Hi, Op 15-mei-07, om 10:23 heeft Tanya M. Lattner het volgende geschreven: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. I did a debug build on OSX 10.4.9 and everything went fine. Results of "make check" (see ppc.log): === Summary === # of expected passes 1630 # of unexpected failures 21 # of expected failures 2