similar to: [LLVMdev] LLVM bitcode for cross-platform plugins

Hello *'s, I have recently installed CentOS v3.3 and i have latest stable Asterisk's source code ,i compiles it shows no error but when i am looking for sip.conf,zapata.conf ,i am amazed the /etc/asterisk folder was empty i am compling several times but no luck what's the problem i compiled in the order of zaptel,libpri,asterisk. I send some traces of my asterisk's compilation

Ubuntu 10.04. Wine 1.2 I'm running Native Instruments Kontakt 4 under Wine. It runs fine except for occasional stutters, so I wanted to try enabling Realtime in Jack, but I have no luck with this. (I have made recommended edits to the limits.conf file, though I've read that this is no longer necessary(?): @audio - rtprio 100, @audio - memlock 250000) When I start up Kontakt, I see

Last week someone in my localnetwork "abused" from our link, making everything slow... So I want to put the current Linux router as a traffic shaper. The setup is: +--- 128Kbit | "International" Local net --- [Linux router with ] -- ISP -- [magic routers]

Yesterday I tried to compile wine asio.I am running debian Squeeze and tried both the lenny and sid wine repos..but on compiling wine asio.it errors out and cant find ..now this was yesterday so i cant remember the exact name ..but it was something like lobc32 ..something like that..maybe logbc32..but anyway..I uninstalled wine and wine-dev..and installed debian version of wine..it 1.0.1 along

Thanx for a prompt reply. I will definitely try llvm 2.8 as per your suggestion. However Step 1 and Step 2 are working for me in case of a simple hello world program on arm processor . Similarly I am able to run a GTK application on arm. However while running wxGTKwidget app it crashes while allocation of memory. As I mentioned earlier, If I explicitly allocate memory using new operation then

On Aug 7, 2009, at 21:48, Didier Dambrin wrote: > FLAC doesn't preserve every chunk? I thought it did. I only gave a > quick try > but it seemed to have preserved even the most obscure chunks. > Let me check: it even seems to preserve "MIDI note associated to > marker", > which is a very unknown metadata used by SoundForge (& even defined > in a >

Hello everybody, I'm currently developing my own small operating system as a hobby project in my free time. Until now, I'm using gcc and the binutils to compile my C++ code. I want to try something new and try to use llvm with clang as a C(++) frontend as a compiler. Unfortunately I couldn't find any information about how I can use clang and llvm in a freestanding environment without

I thought the LLVM IR is target independent and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. -Timo -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at

Dear all, I cannot find the answer of this question. We all know LLVM IR is portable, but it uses ILP32 and record the target layout within the IR. target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64 :64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-linux-gnu" It seems it already assigned

On Apr 7, 2010, at 5:07 PM, Andreas Galauner wrote: > > shouldn't be necessary with llvm since I can just translate the bitcode > to any native architecture http://llvm.org/docs/FAQ.html#platformindependent Dan

> memory. As  I mentioned earlier, If I explicitly allocate memory using new > operation then everything works fine. Please let me know why do we actually > fail without using new, that to a arbitrary pointer which is never used in > the program. x86 and ARM have different ABIs, so you was just lucky. You can read e.g. http://llvm.org/docs/FAQ.html#platformindependent for more

Hello > We all know LLVM IR is portable, but it uses ILP32 No, it doesn't use this. > It seems it already assigned their sizes mapping with types. > How can it be portable? Isn't it been written there? Everything depends on how you generated the IR. You might find this link http://llvm.org/docs/FAQ.html#platformindependent useful. -- With best regards, Anton Korobeynikov

Thanks very much for all of your answer. I was confused by definition of 'portable' by my own thinking. Now I Correct that. (ILP32 is in another project, It's my typo. Thanks) So let me make a conclusion about this. LLVM IR can be a portable language, just depending on our front-end configuration or origin language limits. Did I mistake that? Thank a lot all of you. 2010/12/22

Hi all, A few different though somewhat related questions here. I'm really grateful for your answers! 1. From a previous question I know that sizeof's are resolved into literals early in the front-end before IR is even emitted. It seems that they are resolved into whatever value is correct for the host machine. But if one wishes to then take the IR and emit assembly code for some other

Hi All, I've finished the first draft of the 2.8 release notes: http://llvm.org/docs/ReleaseNotes.html Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I missed something, so if I missed your favorite feature, please speak

Stripf, Timo wrote: > I thought the LLVM IR is target independent Yes. and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. No. > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. LLVM IR contains a target-information line but is otherwise target

On 2010-10-04 06:43, Chris Lattner wrote: > Hi All, > > I've finished the first draft of the 2.8 release notes: > http://llvm.org/docs/ReleaseNotes.html > > Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I

On Jan 29, 2010, at 12:09 PM, Samuel Crow wrote: > Hello Russell, > > Major pitfall #1: > LLVM-GCC does certain optimizations even if all of the optimizations are turned off. These include endian-specific optimizations so to use LLVM as a cross-architecture bitcode, you'll need to wait until Clang supports C++ fully or just stick to C programs for now. > > I've been

On Thu, Oct 27, 2011 at 7:31 AM, Harel Cain <harel.cain at gmail.com> wrote: > Hi all, > > A few different though somewhat related questions here. I'm really grateful > for your answers! > > 1. From a previous question I know that sizeof's are resolved into literals > early in the front-end before IR is even emitted. It seems that they are > resolved into

Stripf, Timo wrote: > I thought the LLVM IR is target independent and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. > > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. > > -Timo LLVM IR is very target dependent. The IR knows about things