search for: brz

Hi All BT are providing a SIP gateway for PSTN through the BT communicator with Yahoo Messenger, I have done an ethereal trace and found that the BT Communicator side of the software is using SIP, so in theory I could add more PSTN lines to Asterisk for BT using SIP, but I am having problems deciphering the trace so my question is has anyone else tried to get BT Communicator work with

...ToReg 0xa908760, 0xa9070e0, 0xa9071f0 <<--<<--<<--<<--<< Node 0xa9095d0: ch,flag = inlineasm 0xa906e30, 0xa908570, 0xa908c60, 0xa9070e0, 0xa9075a0, 0xa9070e0, 0xa906e30:1 SU(2): 0xa909560: ch = CopyToReg 0xa907600:1, 0xa909500, 0xa907600 SU(3): 0xa907ff0: ch = BRZ 0xa907600, 0xa906f10, 0xa909560 0xa906e30: ch,flag = CopyToReg 0xa908760, 0xa9070e0, 0xa9071f0 -scooter On Oct 16, 2007, at 12:00 AM, Evan Cheng wrote: > This is a scheduler assertion. It means a value (virtual register) use > is somehow scheduled before its definition. > > Please...

...9070e0, 0xa9071f0 > <<--<<--<<--<<--<< Node > 0xa9095d0: ch,flag = inlineasm 0xa906e30, 0xa908570, 0xa908c60, > 0xa9070e0, 0xa9075a0, 0xa9070e0, 0xa906e30:1 > SU(2): 0xa909560: ch = CopyToReg 0xa907600:1, 0xa909500, 0xa907600 > SU(3): 0xa907ff0: ch = BRZ 0xa907600, 0xa906f10, 0xa909560 > > 0xa906e30: ch,flag = CopyToReg 0xa908760, 0xa9070e0, 0xa9071f0 > > > -scooter > > On Oct 16, 2007, at 12:00 AM, Evan Cheng wrote: > >> This is a scheduler assertion. It means a value (virtual register) >> use >> is some...

This is a scheduler assertion. It means a value (virtual register) use is somehow scheduled before its definition. Please run llc in gdb. Call dumpSchedule() to print out the schedule. Also please let me know which node it is processing at the time of the assertion. Evan On Oct 15, 2007, at 11:48 PM, Scott Michel <scottm at aero.org> wrote: > Yup, I've got one remaining bug

Yup, I've got one remaining bug that holding up the CellSPU release. It still has a bunch of warts, but so long as I can get it into shape such that llvm-gcc-4.2 compiles all the way through, then we collectively have something with which to work. I'm getting the following error from llc, the attachments have llc's debug and the .ll files, respectively. Can anyone shed some

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