search for: ldx

...d of int, i.e. F77_NAME(dgesvx)(const char* fact, const char* trans, const int* n, My reasoning: In the R-source: src/modules/lapack/dlapack.f I find the following lines: * SUBROUTINE DGESVX( FACT, TRANS, N, NRHS, A, LDA, AF, LDAF, IPIV, * EQUED, R, C, B, LDB, X, LDX, RCOND, FERR, BERR, * WORK, IWORK, INFO ) * * .. Scalar Arguments .. * CHARACTER EQUED, FACT, TRANS * INTEGER INFO, LDA, LDAF, LDB, LDX, N, NRHS * DOUBLE PRECISION RCOND where FACT is specified to a char. Might this simply be...

...redecessors according to CFG: BB#36 %X3<def> = LD 0, <fi#27>; mem:LD8[FixedStack27] %X4<def> = RLDICR %X3<kill>, 3, 60 %X5<def> = LI8 <jt#0>[TF=4] %X5<def> = ADDIS8 %X5<kill>, <jt#0>[TF=8] %X4<def> = LDX %X4<kill>, %X5<kill>; mem:LD8[JumpTable] MTCTR8 %X4<kill>, %CTR8<imp-def,dead> BCTR8 %CTR8<imp-use,kill>, %RM<imp-use> Successors according to CFG: BB#23 BB#15 BB#7 BB#8 BB#9 BB#10 BB#11 BB#25 BB#12 BB#16 BB#18 BB#13 BB#17 How could CRT8 be m...

...g to CFG: BB#36 > %X3<def> = LD 0, <fi#27>; mem:LD8[FixedStack27] > %X4<def> = RLDICR %X3<kill>, 3, 60 > %X5<def> = LI8 <jt#0>[TF=4] > %X5<def> = ADDIS8 %X5<kill>, <jt#0>[TF=8] > %X4<def> = LDX %X4<kill>, %X5<kill>; mem:LD8[JumpTable] > MTCTR8 %X4<kill>, %CTR8<imp-def,dead> > BCTR8 %CTR8<imp-use,kill>, %RM<imp-use> > Successors according to CFG: BB#23 BB#15 BB#7 BB#8 BB#9 BB#10 BB#11 > BB#25 BB#12 BB#16 BB#18 BB#13 BB#17 &gt...

...%X3<def> = LD 0, <fi#27>; mem:LD8[FixedStack27] > > %X4<def> = RLDICR %X3<kill>, 3, 60 > > %X5<def> = LI8 <jt#0>[TF=4] > > %X5<def> = ADDIS8 %X5<kill>, <jt#0>[TF=8] > > %X4<def> = LDX %X4<kill>, %X5<kill>; mem:LD8[JumpTable] > > MTCTR8 %X4<kill>, %CTR8<imp-def,dead> > > BCTR8 %CTR8<imp-use,kill>, %RM<imp-use> > > Successors according to CFG: BB#23 BB#15 BB#7 BB#8 BB#9 BB#10 BB#11 > > BB#25 BB#12 BB#16 B...

I found the problem but not a solution. It turns out if I add the following lines to dqrdc2.f I get the error: write(*,300) ldx,n,p 300 format(3i4) I don't get a compile error but I get the seemingly unrelated error in linking R.DLL I guess the question now is, "How do I add a simple print statement?". Or, what is wrong with the above print statement? Thank you. Kevin

Hi, In Splus if I call the function crosstabs() the output is a contigency table; in each cell of the table is printed: N, N/RowTotal, N/ColTotal, N/Total. N is the number of observations in each cell. The same call to xtabs() in R will produce the contigency table but the only entry in each cell is N. How can I get the same relative frequencies that crosstabs() gives? Thanks, mike --

...stx %sp,[%o0+0] ! Callers stack pointer + stx %o7,[%o0+8] ! Return pc + stx %fp,[%o0+16] ! Frame pointer + retl ! Return + clr %o0 ! ...0 + + .size setjmp,.-setjmp + + + .globl longjmp + .type longjmp, @function +longjmp: + mov %o1, %g4 ! save return value + mov %o0, %g1 ! save target + ldx [%g1+16],%g5 ! get callers frame +1: + cmp %fp, %g5 ! compare against desired frame + bl,a 1b ! if below... + restore ! pop frame and loop + be,a 2f ! if there... + ldx [%g1+0],%o2 ! fetch return %sp + +.Lbotch: + unimp 0 ! ... error ... + +2: + cmp %o2, %sp ! %sp must not decre...

...size_t opts_len); void dlacn2_ (int *n, double *v, double *x, int *isgn, double *est, int *kase, int *isave); void dlaln2_ (int_least32_t *ltrans, int *na, int *nw, double *smin, double *ca, double *a, int *lda, double *d1, double *d2, double *b, int *ldb, double *wr, double *wi, double *x, int *ldx, double *scale, double *xnorm, int *info); void dlabad_ (double *small, double *large); void drscl_ (int *n, double *sa, double *sx, int *incx); void dlatrs_ (char *uplo, char *trans, char *diag, char *normin, int *n, double *a, int *lda, double *x, double *scale, double *cnorm, int *info, size_...

...but better than any other hatchet job you may come up with. Don't do these. For real. They are super fun exercises, but much like linux from scratch, they are painful, hard to maintain, and implementing them would get you removed from my development team. Try following https://gist.github.com/ldx/9116170 but do a cent7 chroot install instead. That would probably work, and you'd be able to patch both systems with regular yum updates. I've done something similar on debian boxes in the past and it surprisingly worked. This is the least bad of the terrible options I've provided (ass...

...a register class (called dp16) of memory locations that while they are not really registers, can be used as such in a lot of situations. However, they are not directly copyable. They require a move to a hardware register and then a store to another dp16 register. Example: lda %w06 sta %w00 -or- ldx %w06 stx %w00 -or- ldy %w06 sty %w06 In short, the A, X, and Y registers are the only practical conduit through which one can copy dp16 "registers". One possible fix to the machine instruction listing would be to put the copy from %w06 to %w00 above the first three lines, thus allowing...

...variable address (0x909ac) is only word-aligned: 58588: 37 00 02 42 sethi %hi(0x90800), %i3 5858c: 40 00 18 1a call 5e5f4 <umac_final> 58590: 92 06 e1 ac add %i3, 0x1ac, %o1 ! 909ac <Bbss.bss> This later causes a crash in: pdf_gen_xor+0x68: ldx [0x909ac], %o5 I am proposing two alternatives for the fix (please, see attached): umac_align-pragma.patch - Solaris Studio specific pragma umac_align-union.patch - generic approach - union for alignment -- You are receiving this mail because: You are watching the assignee of the bug.

I've mentioned my sneaky plans to target the MOS6502 here before. The big issue I think is that a lot of instructions don't really have a choice for output register. It all just goes into the accumulator, X index, or Y index based on the specific instruction. So, my question is, when I'm defining my ins, outs and registers for these instructions, is it going to be a problem that

We have a third party shared library from a vendor that requires glib 2.15 or newer. We are using CentOS 6.6 which comes with glibc 2.12, and I know it can?t be replaced as it?s an integral part of the OS. However, is it possible to build a glib 2.15 RPM from source to be installed in /opt/centos (or somewhere else other than /usr/lib) so that I can link the one application that requires the

...E() is akin to the compiler generated function prologue for * PIC code. It leaves the address of the Global Offset Table in DEST, @@ -83,12 +83,20 @@ 0: \ add dest,%o7,dest; \ mov tmp, %o7 +#define SET(var,base,dest) \ + sethi %gdop_hix22(var), dest; \ + xor dest, %gdop_lox10(var), dest; \ + ldx [base + dest], dest, %gdop(var) #else #define PIC_PROLOGUE(dest,tmp) \ mov %o7,tmp; 3: call 4f; nop; 4: \ sethi %hi(_C_LABEL(_GLOBAL_OFFSET_TABLE_)-(3b-.)),dest; \ or dest,%lo(_C_LABEL(_GLOBAL_OFFSET_TABLE_)-(3b-.)),dest; \ add dest,%o7,dest; mov tmp,%o7 +#define SET(var,base,dest) \ + se...

...E() is akin to the compiler generated function prologue for * PIC code. It leaves the address of the Global Offset Table in DEST, @@ -83,12 +83,20 @@ 0: \ add dest,%o7,dest; \ mov tmp, %o7 +#define SET(var,base,dest) \ + sethi %gdop_hix22(var), dest; \ + xor dest, %gdop_lox10(var), dest; \ + ldx [base + dest], dest, %gdop(var) #else #define PIC_PROLOGUE(dest,tmp) \ mov %o7,tmp; 3: call 4f; nop; 4: \ sethi %hi(_C_LABEL(_GLOBAL_OFFSET_TABLE_)-(3b-.)),dest; \ or dest,%lo(_C_LABEL(_GLOBAL_OFFSET_TABLE_)-(3b-.)),dest; \ add dest,%o7,dest; mov tmp,%o7 +#define SET(var,base,dest) \ + se...

On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote: > > > - figure out Fortran2003 specification for C/Fortran interoperability > > -- this _sounds_ like the right solution, but I don't think many > > understand how to use it and what is implied (in particular, will > > it require making changes to LAPACK itself?) > > That would actually be fairly

Hello! Can someone please help me in building debug version of klibc ? I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but failed to build it with debug info added "-g" to HOSTCFLAGS in Makefile, but $ make -j KLIBCKERNELSRC=`pwd`/../linux-2.6/usr still strips every debug symbol , and i'm failed to change scripts/Kbuild.klibc and Makefile to remove strip

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at:

...vOxO*c#ifXXp2Gn3E>iiKa2ICod=$!{Q|s5yMUZ!$Z61s(Mj2)DfxNEwaONajM6Su z?$h>2q3_XBM{AmLzcxlwmB+NPz&o{ZpggFJ2YytW0Lnw!MBqoX(ZJimsVR?xM^zpG zzozU0kET2f9!=SyO+t&iwaJ>(xL$cuV^fgauT9k$4iwrnO<Y({N6CHK3_;ShnId4? zEb!kzW@}GrgXU;*Qs$!I$J#ti+=k5u&g9wx5jeDknlROiP|ItYkiZw(62#xomZJT) zv}MS>Ldx at 7O-S$)P0Yd9+A7fLRE?|#*E`x8lsKcU71E*WgcP;)z&~mmG`V$c6fGIr zCUBkA?ln8K84O=)TQsr#-ls{8*$UDJ+BV?#we4aKwEM+;YY(8 at G3`Ob-_stFBY4;> z at CZoXX*)z$2zgZ0>(m}IvmQs*d2J_p_p-JN<xgq5&A#jreIeRv(B9UbkYnGgU8X#( z?E~)%+LPiwTM>rhU2VT$)wBbs>Idzhs9rgQVlP6hvW=&aIHw&p6VIUdQSDiwnA#EG z...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking