search for: extinsics

I've just started consulting for a SME client based in Reston Virginia. They don't know it yet but they are going to need a hosted asterisk service and some DID's. Email me if you are able to provide 10 DID's in Reston (must be able to be ported away!!) and hosted Asterisk with end user configurable IVR etc. Probably only 5-8 users at the moment BUT... they'll be

On Feb 27, 2009, at 12:56, Mark Shannon wrote: > Gordon Henriksen wrote: > >> The ultimate endgoal is to support schemes with still-lower >> execution overhead. The next step for LLVM GC would be elimination >> of the reload penalty for using GC intrinsics with a copying >> collector. This, again, requires that the code generator perform >> bookkeeping

I get congestion (same error) with exten => _NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) not dialing 1 exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) dialing 1 exten => _91NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) dialing 9 All the same == Parsing '/etc/asterisk/sip_notify.conf': Found -- Executing [9544790554 at To_Airspring:1]

Gordon Henriksen wrote: > Hi Mark, > > I don't think anyone will dispute that it's easier to hack up a shadow > stack (or plug into a conservative collector) to get up and running > with GC. That is absolutely the route to go if portability trumps > performance. Why? LLVM is all about portability AND performance. > > If you review the mailing list history,

...anything. No one could possibly implement this "specification". Sorry about all my negative comments, but I would like to implement a generational collector for llvm, but I cannot do so in a portable way. So, here is a suggestion: Call the GC 'intrinsics' something else, "extinsics"?, and provide low-level intrinsics so that the GC calls, gcroot, gcread and gcwrite can be converted to GC-free LLVM code in a GC-lowering pass. IR+GC -> | GC Lowering pass | -> IR Rather than than the current. IR+GC -> | Backend lowering pass(es) | -> SelectionDAG Read and...