search for: ropy

I am running R 2.1.1 on a Mac g5 under Mac OS 10.4.2. I have an xyplot with a single conditioning variable (8 levels) . Here is the code for the conditioning variable used in the formula argument of xyplot: factor( drugauthoryear, levels = c( 'bupicapogna1999', 'levobenhamou2003', 'ropicapogna1999',

Hi, We currently have a downstream patch (attached) which implements some new addressing modes that enable position-independent code for small embedded systems. Is this something that would be accepted upstream? I think the ARM backend changes are fairly uncontroversial, but the clang changes introduce a lot of ROPI/RWPI specific changes in otherwise target-independent code. If the clang changes

Hi all, I'm trying to see if I can use a global static base register instead of PC-relative addressing. I see that I can easily reserve R9 in the ARM Subtarget, but this doesn't let me use it. I found a TODO in ARMAsmPrinter.cpp that refers to this: // TODO: We currently only support either reserving the register, or treating // it as another callee-saved register, but not as SB or a

...r from FC7 to FC9 and with it came Samba 3.2.0pre3-9.fc9 (heaven knows why it had to be a pre version). I reused my old config and noticed that displaying all hosts in my workgroup as well as authentication went from normal to awfully slow. Once the connection is established it is bearable, though ropy. smbclient -L samsara //from an Ubuntu 8.04 in the same network smbclient -L localhost //from the server itself results in: Receiving SMB: Server stopped responding session setup failed: Call timed out: server did not respond after 20000 milliseconds I have been reading a lot about it, i found...

Hi, Sam. I think that it's a fair comparison. Keep in mind that the GP is only used to reach global variables of local scope and the GOT, where the address of global variables of global scope reside. This model assumes that the distance between the GP and the global data area, GOT and local scope variables is defined at link time. __ Evandro Menezes ◊ SiFive ◊ Austin, TX > On Mar

...?ch v?robk?', 'Zpracov?n? d?eva a v?roba d?ev?n?ch v?robk? krom? n?bytku', 'V?roba v?robk? z pap?ru; vydavatelstv? a tisk', 'V?roba chemick?ch l?tek, p??pravk?, v?robk? a chemick?ch vl?ken', 'V?roba pry?ov?ch a plastov?ch v?robk?', 'Rafin?rsk? zpracov?n? ropy', 'V?roba stroj? a za??zen? j.n.', 'V?roba elektrick?ch a optick?ch p??stroj? a za??zen?', 'V?roba ostatn?ch nekovov?ch miner?ln?ch v?robk?', 'V?roba z?kladn?ch kov?, hutn?ch a kovod?ln?ch v?robk?', 'V?roba dopravn?ch prost?edk? a za??zen?','Zpr...

Oh, I wasn’t really thinking about devices without an MMU where the addresses are physically separated. Makes sense. This reminds me of rwpi on ARM; it has a sort of similar scheme of referring to data indirectly through a pointer, but it also changes the ABI to keep the pointer in a reserved register. -Eli From: Evandro Menezes <evandro.menezes at sifive.com> Sent: Friday, March 20, 2020

...ed as a setting for SPEEX_SET_QUALITY > and SPEEX_SET_COMPLEXITY, the (*(int*)ptr) always = 0. For quality this > doesn't matter I don't think due to the default settings, but the > st->complexity always ended up as zero, and the decoded bit-stream ends up > sounding very ropy. Actually, I don't see why long/int would be a problem here since you're also passing an (int*) and the values are never higher than 32767. > I think this the issue Jim alluded to in his question 2 > regarding 'artifacts'. I don't think it was artifacts but perhaps thi...

...EEX_SET_QUALITY >> and SPEEX_SET_COMPLEXITY, the (*(int*)ptr) always = 0. For quality this >> doesn't matter I don't think due to the default settings, but the >> st->complexity always ended up as zero, and the decoded bit-stream ends >> up >> sounding very ropy. > > Actually, I don't see why long/int would be a problem here since you're > also passing an (int*) and the values are never higher than 32767. This suggests that the problem is in the calling routine. >> I think this the issue Jim alluded to in his question 2 >> re...

...matter what you passed as a setting for SPEEX_SET_QUALITY and SPEEX_SET_COMPLEXITY, the (*(int*)ptr) always = 0. For quality this doesn't matter I don't think due to the default settings, but the st->complexity always ended up as zero, and the decoded bit-stream ends up sounding very ropy. I think this the issue Jim alluded to in his question 2 regarding 'artifacts'. I don't think it was artifacts but perhaps this issue I have described. In nb_celp.c I changed all those effected (*(int*)ptr) to long, but perhaps it would be better to have a more platform independant...