search for: backword

Hello, In regard to the review request https://reviews.llvm.org/D74470, I am trying to move five of the DIFlags to DISPFlag for the moment namely DIFlagExplicit, DIFlagPrototyped, DIFlagNoReturn, DIFlagThunk, DIFlagAllCallsDescribed. The llvm ir format for DISubprogram currently has backword compatibility where the isLocal, isDefinition, virtuality, isOptimized and SPFlags are mutually exclusive. My question is, is it a good idea to remove the booleans support'(isLocal, isDefinition) and move most of it to spflags and flags in llvm ir? The llvm ir backward compatibility does not li...

...In regard to the review request https://reviews.llvm.org/D74470, > > I am trying to move five of the DIFlags to DISPFlag for the moment namely DIFlagExplicit, DIFlagPrototyped, DIFlagNoReturn, DIFlagThunk, DIFlagAllCallsDescribed. > > The llvm ir format for DISubprogram currently has backword compatibility where the isLocal, isDefinition, virtuality, isOptimized and SPFlags are mutually exclusive. > > My question is, > > is it a good idea to remove the booleans support'(isLocal, isDefinition) and move most of it to spflags and flags in llvm ir? But it was already &qu...

...the review request https://reviews.llvm.org/D74470, >> >> I am trying to move five of the DIFlags to DISPFlag for the moment namely DIFlagExplicit, DIFlagPrototyped, DIFlagNoReturn, DIFlagThunk, DIFlagAllCallsDescribed. >> >> The llvm ir format for DISubprogram currently has backword compatibility where the isLocal, isDefinition, virtuality, isOptimized and SPFlags are mutually exclusive. >> >> My question is, >> >> is it a good idea to remove the booleans support'(isLocal, isDefinition) and move most of it to spflags and flags in llvm ir? > &gt...

...ction, I would maybe try something like this: > > > [general] > > port = 5060 ; Port to bind to > > context=sip-extensions > > externip = xxx.xxx.xxx.xxx > > localnet = 192.168.1.0/24 > > localmask is no longer used. Not sure if there is backwords > compatibility (and I'm doing this from memory, I don't have Asterisk > behind NAT anymore) > > I don't know, maybe it will work, maybe it won't :) > > HTH, > Leif Madsen > http://www.asteriskdocs.org > > --__--__--

...this: > > > > > [general] > > > port = 5060 ; Port to bind to > > > context=sip-extensions > > > externip = xxx.xxx.xxx.xxx > > > localnet = 192.168.1.0/24 > > > > localmask is no longer used. Not sure if there is backwords > > compatibility (and I'm doing this from memory, I don't have Asterisk > > behind NAT anymore) > > > > I don't know, maybe it will work, maybe it won't :) > > > > HTH, > > Leif Madsen > > http://www.asteriskdocs.org > > &gt...

This has probably been answered somewhere, but I'm stumped. I have two Zap channels (FXS and FXO), both working fine. I can call from Zap/1 to Zap/2 and reverse. I've also configured SIP channels, both inside and outside of my firewall. Inside can call outside, and outside can call inside. Also, both inside and outside can make and receive calls to/from Zap/1 & Zap/2. What

...so you understand, I am pasting below some of the generated SSE code for the fir_mem2_10 function. I got this by compiling the speexenc and loading it up in the debugger. Skipped a bit of the initial function stuff the block starts inside the for loop. For those who don't know, Win32 asm is backwords from GCC, it is OPERATION DEST, SOURCE 254: for (i=0;i<N;i++) 255: { 256: __m128 xx; 257: __m128 yy; 258: /* Compute next filter result */ 259: xx = _mm_load_ps1(x+i); 00413483 mov eax,dword ptr [ebp-64h] 00413486 mov ecx,dword ptr [e...

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)