search for: stosw

Hi all, I'm trying to compile asterisk on the mainframe (s390 / s390x) and I am running into issues. I was wondering if somebody could give a hand? I'm thinking that I should be able to do this. I have noticed that Debian even has binary RPM's out for Asterisk now. I'm trying to do this on SuSE SLES8 (with the 2.4 kernel). What I see is, an issue that arch=s390 isn't

...uot;D" (res_buf), "a" (p), "c" (16) + : "memory", "cc", "rdx" + ); +#else + __asm__ __volatile__( + "mov %%edi,%%edx\n" /* I cant tell the GCC that EDI value is clobbered */ + "cld\n" + "rep\n" + "stosw\n" + "mov %%edx,%%edi\n" /* I cant tell the GCC that EDI value is clobbered */ + : + : "D" (res_buf), "a" (p), "c" (64) + : "memory", "%edx", "cc" + ); +#endif + } + else{ + + /*Then, fill in the rema...

...t;movs"); - return DECODE_success; - + case 0xaa: + /* stosb */ + thread_inst->op_size = BYTE; + strcpy((char *)thread_inst->i_name, "stosb"); + return DECODE_success; + case 0xab: + /* stosw/stosl */ + if (thread_inst->op_size == WORD) { + strcpy((char *)thread_inst->i_name, "stosw"); + } else { + thread_inst->op_size = LONG; + strcpy((char *)thread_inst->i_name, "stosl"); + }...

Hi, I recently ran into an issue where the dependencies generated in modules.dep created a circular reference, which meant that qemu spun forever in modules_load_dependencies(). I did think about detecting this kind of circular dependency at modules.dep generation time but if we ever move to using DT_NEEDED to track dependencies we would need this functionality in the elflink core anyway.