similar to: [LLVMdev] llc: for the -march option: : Cannot find option named 'c'!

You're right, thanks. However, now I ran into the next problem. This seems to be related to the fact that I have a 64-bit machine? $ ../../src/llvm-gcc/configure --prefix=/home/johan/llvm --program-prefix=llvm- --enable-llvm=/home/johan/llvm/obj/llvm --enable-languages=c,c++ ... $ gmake ... /home/johan/llvm/obj/llvm-gcc/./gcc/xgcc -B/home/johan/llvm/obj/llvm-gcc/./gcc/

On 2008-11-18 12:22, Johan Cockx wrote: > You're right, thanks. However, now I ran into the next problem. > This seems to be related to the fact that I have a 64-bit machine? > > $ ../../src/llvm-gcc/configure --prefix=/home/johan/llvm > --program-prefix=llvm- --enable-llvm=/home/johan/ > llvm/obj/llvm --enable-languages=c,c++ Use --disable-multilib --Edwin

llvm-gcc 2.4 doesn't seem to compile; what is wrong? This is my first attempt to compile llvm-gcc. The llvm core compiled without problems. $ uname -a Linux ygramoel 2.6.26.5-45.fc9.x86_64 #1 SMP Sat Sep 20 03:23:12 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux $ gcc -v ... gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) $ svn co

Hello friends working on LLVM, I am a beginner to LLVM. I tried to get C code from LLVM bitcode using 'llc -march=c'. But it seems to me that it doesn't work if the source program is a C++ program. Am I right? I have attatched the source program and the result of compiling the C code of it with GCC4.3.3. By the way, has LLVM's C code backend been tested on benchmarks like spec?

I'm trying to play a wav-file on a channel. This is what I see in the asterisk debug console AGI Rx << STREAM FILE "test.wav" "12345" [Aug 20 16:10:19] WARNING[25219]: file.c:602 ast_openstream_full: File test.wav does not exist in any format So it doesn't find the file, or it's in a wrong format? I can listen to it with windows media player... it's a

It is expected and not unusual to need to update the lit test in such case. I'd need to see exactly which test breaks and how to know though. Best, -- Mehdi 2017-09-18 13:17 GMT-07:00 Johan Engelen <jbc.engelen at gmail.com>: > The fix (https://reviews.llvm.org/D37961) does not work. From what I > have learned thusfar, the module identifier is used as filename sometimes >

Hello, I would like to ask the llvm developers to have a look at http:// llvm.org/bugs/show_bug.cgi?id=918 . This bug has been reported 4 month ago but is none the less a somewhat serious one. Below I have pasted the test case and output of the issue running on my ppc machine. thank you Eric pb:~ eric$ cat testme.ll;llvm-as -f testme.ll;llc -march=c -f testme.bc;gcc -c testme.cbe.c

The fix (https://reviews.llvm.org/D37961) does not work. From what I have learned thusfar, the module identifier is used as filename sometimes (I think when writing an intermediate module index summary), and so a bunch of lit tests fail with the "fix". I'll look further into fixing this, any help is appreciated. ( One thing that may be important is to have a deterministic suffix.

I've created a review for your patch Mehdi: https://reviews.llvm.org/D37961 First time using `arc`, so hope things went well. - Johan On Tue, Sep 12, 2017 at 5:25 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: > Hi Johan, > > 2017-09-11 14:21 GMT-07:00 Johan Engelen <jbc.engelen at gmail.com>: > >> On Fri, Sep 8, 2017 at 9:04 PM, Johan Engelen

Hello, I am new in using llvm so I would like to get some help on how to compile test-suite. Assumptions: llvm is in /llvm directory llvm-gcc is in /llvm-4.2-2.4-x86-linux-RHEL4/bin I have tried compiling test-suite and I get the following error: $make make[1]: Entering directory '/llvm/projects/test-suite/SingleSource' make[2]: Entering directory

Hello everyone, I've been trying to generate a C file using the llc tool, but I'm having a problem. I'm using a single Hello World program in C, and executing the following passes: clang -emit-llvm -c -o hello.bc hello.c  # getting the bit code of hello.c llc -march=c hello.bc                          # generating the hello.cbe.c file using the llvm C backend So far, nothing weird

On Fri, Sep 8, 2017 at 9:04 PM, Johan Engelen <jbc.engelen at gmail.com> wrote: > > On Thu, Sep 7, 2017 at 5:44 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > >> Hi Johan, >> >> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >> in llvm/tools/lto/lto.cpp) >> >> For instance ThinLTOCodeGenerator::addModule is called

Hi Cristianno, This problem has been around for a while, ourselves we solve it with the following patches: https://hpcforge.org/scm/viewvc.php/trunk/patches/llvm.gpu.patch?root=kernelgen&view=markup https://hpcforge.org/scm/viewvc.php/trunk/patches/llvm.patch?revision=591&root=kernelgen&view=markup Please feel free to apply them, they *should* work for you even with the latest llvm

Hi, Finally, I have launched "yum downgrade samba*" too for best effort. I am waiting for news until my samba 4 migration. AC-GUYANE <mailto:Johan.Glenac at ac-guyane.fr> *Johan GLENAC* *DSI* Administrateur Système, Réseaux et Télécom *TROUBIRAN :* Route de Baduel - BP 6011 97306 Cayenne *Tél. :* +594 (0) 594 27 22 08 *Fax :* +594 (0) 594 27 22 20 Rectorat - Académie de la

Hello again, Thanks for the responses =) Dmitry, I have two points to comment: - First, I applied these two patches, and the .cbe.c file came out ok, except for one little thing -- the global variable was created with both modifiers: static and extern. Then, I just added a single guard to prevent this to happen (in a case of a variable having local linkage, the "extern" part was not

The PGO was my first guess but I can get a lot of information. At first, I follow the explanation at http://clang.llvm.org/docs/UsersManual.html#profiling-with-instrumentation but instead of llvm-profdata merge, I used llvm-profdata show *.profraw. Sadly, the information I get is the total number of function, the maximum function count and the maximum internal block count. Do you know if you

Yeah I have already see pintool but I need this to work with ARM and Intel. If I remember correctly, pintool does not work on ARM (or quite bad). My goal with the instrumentation is, once I have the information (time + call), to choose (during a second compilation) if some of my passes are applicable or not. Greetings, Johan On 17 Jul 2015, at 16:09, Kenneth Adam Miller <kennethadammiller

Humm... Seems like my message didn't make it. Here we go again.. /Johan -------- Original Message -------- Subject: Re: [asterisk-users] ControlPlayback's options Date: Sun, 05 Jun 2011 22:19:18 +0200 From: Johan Wilfer <lists at jttech.se> To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users at lists.digium.com> On 2011-06-05 19:54, virendra

Hi all, I met an error when I run the llc command to transform a bitcode file to C code (source to source): $ llc -march=c -o foo.c foo.ll However, it said "*llc: error: invalid target 'c'.*" I checked the 'llc --version' only to find that there is no *c* as target. The *cpp* was there, which makes calls against the LLVM C++ API. But that's not what I want. I

On Mon, 15 Jan 2007, Nick Lewycky wrote: > Eric van Riet Paap wrote: >> *testme.cbe.c:106: error: array type has incomplete element type* > > The problem code boils down to: > > /* Structure forward decls */ > struct l_structtype_s; > > /* Typedefs */ > typedef struct l_structtype_s l_fixarray_array3[3]; > > which is illegal C, but perfectly valid C++,