similar to: [LLVMdev] Crash in llvm::JITDwarfEmitter::EmitDwarfTable on 2.8 and 2.9 release but not on trunk?

I found the problem : my code sets JITEmitDebugInfo after creating the JIT. This causes the JITDwarfEmitter DE to not be constructed in the ctor of JITEmitter (JITEmitter.cpp around line 375). Not sure if it's documented anywhere that JITEmitDebugInfo must be set before constructing the JIT, but looking at the code, it makes sense. Easy enough to fix on my side. Christophe On 19 avr. 2011,

Hi list, Here it is: I have compiled with no problem courier-imap-4.0.4 on this arch (x86_64). Now I want to update my install with 4.0.6. I want to do this because the server is not yet in a production state, so if a major flaw affects courier-imap in the future, I could react more quickly. And indeed I'm encountering problems with the make process (Since I initialy build courier-imap

Once upon a time, John R Pierce <pierce at hogranch.com> said: > do note, if this is a stage grade electric piano, using big phone > plugs, the audio level out is not quite the same as consumer line > level that a computer input would want to record, you'll likely have > to crank the recording level way up, increasing the noise floor of > the recordings. the cure for

> Well, I thought about it as well but up to now didn't try. Via which > way do you intend to have e.g. a line-in to the iPaq with reasonable > quality. Would be really interesting to figure out such things ... > and then use a WLAN-cradle to transport data to the internet *g* The main use would be covering events at sports fields, auditoriums, etc. that are away from the

I am debugging the memory issue that manifests itself like this: *** glibc detected *** ../app/app.OWS: free(): invalid pointer: 0x0ad391fc *** ======= Backtrace: ========= /lib/libc.so.6(+0x6c501)[0x4f6501] /lib/libc.so.6(+0x6dd70)[0x4f7d70] /lib/libc.so.6(cfree+0x6d)[0x4fae5d] ../app/app.OWS(_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE5eraseESt17_Rb_tree_iteratorIjES7_+0x4b)[0x83de6eb]

Hi, In our design of Icecast2, our multiple sources will stream their high quality audio via a dedicated audio encoder (not a computer): Live audio > L+R microphone > pre amplifier > audio encoder > Icecast2 VPS So far I have a shortlist of 4 possible brands of audio encoders: Sonifex PS-SEND, Barix Instreamer, Bric-Link, Outcaster OC100. All have their pro's and cons.

Hello, I'm trying to port the XL compiler (http://xlr.sf.net) to use the LLVM back-end. So far, little trouble doing so. But there is one aspect of the semantics of the LLVM IR that surprises me. Why are the call, declare and define "halfway through" ABI conventions? I think it's the right thing to have a single high level node for each call, as opposed to separate

I was about to post a bug concerning this, but I thought I'd check with you folks first. The symptom is a SIGSEGV in my program in the standard library template for red black trees (bits/stl_tree.h). The crash occurs as the result of an LLVM Module method, getConstantPointerRef which looks like: // Accessor for the underlying GlobalValRefMap... ConstantPointerRef

Hi James, > want to send us your testcase code? Then we can give it a whirl. > > > Test code is at http://giantblob.com/ehtest.tar.gz > > Thanks for the help. I apologize in advance if it turns out I'm doing > something stupid! I hope you realise that by running llvm-ld without -native you are actually executing your program from the JIT. I did a native

2010/1/22 Duncan Sands <baldrick at free.fr> > Hi James, > > > want to send us your testcase code? Then we can give it a whirl. >> >> >> Test code is at http://giantblob.com/ehtest.tar.gz >> >> Thanks for the help. I apologize in advance if it turns out I'm doing >> something stupid! >> > > I hope you realise that by

2010/1/22 James Williams <junk at giantblob.com> > > > 2010/1/22 Duncan Sands <baldrick at free.fr> > >> Hi James, >> >> >> want to send us your testcase code? Then we can give it a whirl. >>> >>> >>> Test code is at http://giantblob.com/ehtest.tar.gz >>> >>> Thanks for the help. I apologize in

I have some exception handling which works fine using the JIT. Now I am producing object files and linking them, but the exception handling tables seem to be missing. I call _Unwind_RaiseException and get _URC_END_OF_STACK as a result. I produce my object file using TargetMachine::addPassesToEmitFile and then I link my resulting files with: gcc -o prog input.o -fexceptions I'm sure I'm

Looks sane. Thanks. Evan On Feb 1, 2008, at 1:24 AM, Nicolas Geoffray wrote: > Dear all, > > Here's a new patch with Evan's comments (thx Evan!) and some cleanups. > Now the (duplicated) exception handling code is in a new file: > lib/ExecutionEngine/JIT/JITDwarfEmitter. > > This patch should work on linux/x86 and linux/ppc (tested). > > Nicolas > Index:

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL:

Hi James, Note that the wiki example is a manual JIT example that works directly with the C++ APIs. As you know, no LLVM tools are used, just LLVM libraries. I say this to point out, that in the example, the exception mechanism is under the complete control of the developer moded by the LLVM libraries. In my mind a different example/different doc. would be needed to explain how a bit code

Dear LLVMers, I am trying to fold memory operands in the way that is done in RegAllocLocal.cpp, or in LiveIntervalAnalysis.cpp, but I am getting errors that I don't know how to fix. Could someone tell me which steps should I take in order to correctly fold memory operands? The code that I am using is: const TargetMachine & target_machine = this->machine_function->getTarget();

2010/1/22 Duncan Sands <baldrick at free.fr> > Hi James, > > > Yes - sorry I was unclear. I have pruned everything down to a pretty >> minimal test: >> - LLVM 2.6 compiled from source >> - A slightly modified version of Duncan's example ll assembly posted >> earlier >> - A minimal personality function (just a call to fprintf()) in a separate

Hi, Probably some of the leaks Valgrind reports are spurious, but the numbers seem to be significant enough to demand some attention: ==10132== LEAK SUMMARY: ==10132== definitely lost: 15,624 bytes in 558 blocks. ==10132== indirectly lost: 44,548 bytes in 1,591 blocks. ==10132== possibly lost: 37,576 bytes in 98 blocks. ==10132== still reachable: 1,336,876 bytes in 1,364 blocks.

On Tue, 23 Jun 2015 10:15:35 -0400 Lamar Owen wrote: > The USB MIDI port won't give you audio, just MIDI text. That's what I thought. To this point, I've never done anything MIDI and I really don't know much about that; I just use my piano for the purpose of playing the piano. > What sort of sound card do you have? description: Audio device product: 6

On 6/23/2015 2:05 PM, Frank Cox wrote: > I'll have to dig out the manual for my piano and do a bit of reading to see what's really going on with those plugs and whatnot. The only thing I've ever plugged into it so far is headphones. if you can plug in headphones, then you can plug it into a computer line-in jack with a suitable cable, just set the headphone volume on the piano