Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Compiling llvm and Clang on Linux"
2012 Jul 15
0
[LLVMdev] Compiling llvm and Clang on Linux
I tried
CC=gcc44 CXX=g++44 ../llvm/configure
and got
CC=gcc44: Command not found
So the syntax is indeed as wriiten in the help.
Sitvanit Ruah
Formal Verification Group
IBM Haifa Research Laboratory
Tel: 972-4-828-1249
From: Duncan Sands <baldrick at free.fr>
To: Sitvanit Ruah/Haifa/IBM at IBMIL,
Cc: Konstantin Tokarev <annulen at yandex.ru>, llvmdev at cs.uiuc.edu,
2012 Jul 13
2
[LLVMdev] Compiling llvm and Clang on Linux
Hi Sitvanit,
On 12/07/12 22:18, Sitvanit Ruah wrote:
> I ran "configure -help " and it says
>
> usage: configure [OPTION]..... [VAR=VALUE]
>
> So I assume configure CC=... is the right syntax. Isn't it?
while you might think so, try it the other way round. Also, by doing
make VERBOSE=1
you can see which compiler is really being used.
Ciao, Duncan.
>
>
2012 Jul 12
0
[LLVMdev] Compiling llvm and Clang on Linux
I ran "configure -help " and it says
usage: configure [OPTION]..... [VAR=VALUE]
So I assume configure CC=... is the right syntax. Isn't it?
Regard,
Sitvanit
From: Konstantin Tokarev <annulen at yandex.ru>
To: Sitvanit Ruah/Haifa/IBM at IBMIL,
Cc: llvmdev-bounces at cs.uiuc.edu, llvmdev at cs.uiuc.edu, Duncan Sands
<baldrick at free.fr>
Date:
2012 Jul 12
2
[LLVMdev] Compiling llvm and Clang on Linux
> Yes, it is the same error referring to 4.1.2.
>
> /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+
> +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref
> declaration must have internal
> linkage
> __gthrw(pthread_key_delete)
>
> There are several such errors.
Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g++44
2012 Jul 15
2
[LLVMdev] Compiling llvm and Clang on Linux
Hi Sitvanit,
> I tried
>
> CC=gcc44 CXX=g++44 ../llvm/configure
>
> and got
>
> CC=gcc44: Command not found
>
> So the syntax is indeed as wriiten in the help.
actually, no, this just means that you are using a shell that doesn't support
this syntax. What shell are you using? Try
export CC=gcc44
export CXX=g++44
../llvm/configure
Ciao, Duncan.
>
2013 Oct 06
3
[LLVMdev] LLVM 3.3 in llvm.org Ubuntu APT repository
On Sun, Oct 6, 2013 at 6:12 PM, Konstantin Tokarev <annulen at yandex.ru> wrote:
>> It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise
>> APT repository, http://llvm.org/apt/precise/.
>>
>> Is this on purpose? Any recommended replacements? (Launchpad?)
>
> http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary
Sorry, but
2013 Oct 06
2
[LLVMdev] LLVM 3.3 in llvm.org Ubuntu APT repository
Sylvestre (CC'd) might know where to find it on Debian/Ubuntu repositories.
cheers,
--renato
On 6 October 2013 18:45, Alp Toker <alp at nuanti.com> wrote:
> Konstantin, This is a legitimate question because the packages are
> maintained by the LLVM project and kept on llvm.org.
>
> David, while I don't see 3.3 packages I do see 3.4 snapshots in the
> repository.
2013 Oct 06
0
[LLVMdev] LLVM 3.3 in llvm.org Ubuntu APT repository
Konstantin, This is a legitimate question because the packages are
maintained by the LLVM project and kept on llvm.org.
David, while I don't see 3.3 packages I do see 3.4 snapshots in the
repository. Will that not do?
If there are any regressions keeping you back on 3.3 now's a good time
to report them!
Alp.
On 06/10/2013 18:22, David Nadlinger wrote:
> On Sun, Oct 6, 2013 at 6:12
2012 Aug 02
0
[LLVMdev] Reading the output of clang
What is the best level to use for backend development? We do not need to
generate machine code, but rather an intermediate representation that will
give us the control flow graph.
Is this the llvm IR?
If so, how do I read into memory a file that was generated by clang++
-emit-llvm <source file>.
Thanks,
Sitvanit
Sitvanit Ruah
Formal Verification Group
IBM Haifa Research Laboratory
Tel:
2013 Oct 06
0
[LLVMdev] LLVM 3.3 in llvm.org Ubuntu APT repository
Hello,
I did some cleanup of the repositories today (Sunday).
I remove all the 3.3 snapshots which were wrong (they were older than
the official 3.3 release and not maintained).
I didn't think that anybody was using them (Looks like I was wrong, sorry!).
You are not happy about the 3.4 packages ?
Sylvestre
On 06/10/2013 19:52, Renato Golin wrote:
> Sylvestre (CC'd) might know where
2012 Aug 01
3
[LLVMdev] Reading the AST from the bitcode generated by clang
> Hi all,
> After reading the documentation on clang I still have the following
> question:
> How do I read the bitcode generated by clang from a C++ file? I need to
> have all the AST information in memory.
AST has nothing to do with LLVM bitcode.
--
Regards,
Konstantin
2013 Oct 06
0
[LLVMdev] LLVM 3.3 in llvm.org Ubuntu APT repository
06.10.2013, 18:44, "David Nadlinger" <code at klickverbot.at>:
> Hi all,
>
> It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise
> APT repository, http://llvm.org/apt/precise/.
>
> Is this on purpose? Any recommended replacements? (Launchpad?)
http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary
--
Regards,
Konstantin
2012 Jun 29
0
[LLVMdev] Problem compiling with clang + gold plugin: no archive symbol table
I'm trying to enumerate different combinations to get a workable solution.
At least this combination passed the previously failed step, but got stuck
in later ones.
Also my GCC is still 4.5, so llvm 3.0 is not that outdated?
Regards,
Ryan
On Fri, Jun 29, 2012 at 2:07 AM, Konstantin Tokarev <annulen at yandex.ru>wrote:
>
> 29.06.2012, 12:17, "ryan" <stdstack at
2012 Jun 29
2
[LLVMdev] Problem compiling with clang + gold plugin: no archive symbol table
29.06.2012, 12:17, "ryan" <stdstack at gmail.com>:
> I tried some other configurations. Now with llvm 3.0 + clang 3.0, and expoert CC to be clang -flto -use-gold-plugin,and other ENV variables.
> Good news is the "no archive symbol error message" is gone, but bad news is new error messages appear
Why are you using outdated llvm and clang?
--
Regards,
Konstantin
2016 Aug 19
2
OT: Cloning llvm repo over low speed connection != fun
19.08.2016, 18:38, "Renato Golin" <renato.golin at linaro.org>:
> On 19 August 2016 at 16:34, Konstantin Tokarev <annulen at yandex.ru> wrote:
>>> But that affected *everybody*. Using Git or SVN, using Windows or
>>> Linux, trying to download Linux, LLVM, GCC, Linaro stuff.
>>
>> But with SVN you don't fetch complete history.
>
>
2013 Sep 19
2
[LLVMdev] LLVM virtual machine
Hi Konstantin,
good point.
but I my intention is to have something like the llva project.
Basically I would like to define a machine that looks as if it has processors running natively llvm code.
And when that runs enhance the llvm byte code with some specific instructions.
Besides this if I make my measurements on the running of llvm bytecode I can test several platforms simultaneously because I
2012 Dec 03
3
[LLVMdev] Minimum Python Version
03.12.2012, 11:44, "Marc J. Driftmeyer" <mjd at reanimality.com>:
> One of the most conservative distributions is Debian.
RHEL/CentOS is more conservative. RHEL 6 ships Python 2.6.6, RHEL 5 (which is still widely used) ships 2.4.3
--
Regards,
Konstantin
2013 Sep 19
0
[LLVMdev] LLVM virtual machine
On 9/19/13 9:53 AM, Herbei Dacian wrote:
>
> Hi Konstantin,
> good point.
> but I my intention is to have something like the llva project.
If you want something like the LLVA project for user-space applications,
then you basically want to use LLVM as-is. The only things missing are
the instructions that replace certain in-line assembly sequences that
cannot be represented by
2012 Aug 15
0
[LLVMdev] C++ demangling in LLVM
> -----Original Message-----
> From: Konstantin Tokarev [mailto:annulen at yandex.ru]
> Sent: Wednesday, August 15, 2012 9:10 AM
> To: Villmow, Micah
> Cc: Chris Lattner; Dmitry Vyukov; LLVM Developers Mailing List
> Subject: Re: [LLVMdev] C++ demangling in LLVM
>
>
>
> 15.08.2012, 19:25, "Villmow, Micah" <Micah.Villmow at amd.com>:
> > Three
2012 Aug 15
2
[LLVMdev] C++ demangling in LLVM
15.08.2012, 19:25, "Villmow, Micah" <Micah.Villmow at amd.com>:
> Three reasons.
> 1) I need to modify the code to support extensions to the standard demangler.
> 2) GCC's version is GPL v3.
And?
BTW, there is BSD-licensed implementation of __cxa_demangle in libcxxrt
> 3) Need windows support.
>
> Micah
--
Regards,
Konstantin