search for: inputregs

...BX PXE function number ES:DI PXE data buffer Output: AX PXE return status code or, in com32 terms (the PXE call argument struct has been copied into the bounce buffer and the buffer field of the PXE call argument struct is setup to point into the bounce buffer as well): inputRegs.es = SEG(__com32.cs_bounce); inputRegs.edi.w[0] = OFFS(__com32.cs_bounce); inputRegs.eax.w[0] = 0x0009; /* call PXE stack */ inputRegs.ebx.w[0] = 0x0071; /* PXENV_GET_CACHED_INFO opcode */ __intcall(0x22, &inputRegs, &outputRegs); However, when setup this way, ...

...t_addr("255.255.255.255"); // inet_addr working here? args.gw = inet_addr("0.0.0.0"); args.src_port = 4711; args.dst_port = 4799; args.buffer_size = <some sizeof() code> args.buffer = <some stuff to put my data in> memcpy(__com32.cs_bounce, &args, sizeof(args); inputRegs.es = SEG(__com32.cs_bounce); inputRegs.edi.w[0] = OFFS(__com32.cs_bounce); inputRegs.eax.w[0] = 0x0009; /* call PXE stack */ inputRegs.ebx.w[0] = 0x0033; /* PXENV_UDP_WRITE opcode */ __intcall(0x22, &inputRegs, NULL); // code end Could anyone give me a hand on that? Or is there any example a...

2005/7/24, Chris Lattner <sabre at nondot.org>: > Ah, ok. In that case, you want to put all of the registers in one register > file, and not make the constant register allocatable (e.g. see > X86RegisterInfo.td, and note how the register classes include EBP and ESP, > but do not register allocate them (through the definition of > allocation_order_end()). > > -Chris

...t_addr working here? > args.gw = inet_addr("0.0.0.0"); > args.src_port = 4711; > args.dst_port = 4799; > args.buffer_size = <some sizeof() code> > args.buffer = <some stuff to put my data in> > > memcpy(__com32.cs_bounce, &args, sizeof(args); > > inputRegs.es = SEG(__com32.cs_bounce); > inputRegs.edi.w[0] = OFFS(__com32.cs_bounce); > inputRegs.eax.w[0] = 0x0009; /* call PXE stack */ > inputRegs.ebx.w[0] = 0x0033; /* PXENV_UDP_WRITE opcode */ > > __intcall(0x22, &inputRegs, NULL); > // code end > > Could anyone give me a h...

On Sat, 23 Jul 2005, Tzu-Chien Chiu wrote: > 2005/7/23, Chris Lattner <sabre at nondot.org>: >> What does a 'read only' register mean? Is it a constant (e.g. returns >> 1.0)? Otherwise, how can it be a useful value? > > Yes, it's a constant register. > > Because the instruction cannot contain an immediate value, a constant > value may be stored in

2005/7/23, Chris Lattner <sabre at nondot.org>: > > What does a 'read only' register mean? Is it a constant (e.g. returns > 1.0)? Otherwise, how can it be a useful value? Yes, it's a constant register. Because the instruction cannot contain an immediate value, a constant value may be stored in a constant register, and it's defined _before_ the program starts by

...sn't handled and the function returns <pair>(0, NULL). However, it is explicitly called for that constraint by llvm::SelectionDAGLowering::visitInlineAsm(): if (OpInfo.ConstraintType == TargetLowering::C_RegisterClass) GetRegistersForValue(OpInfo, SawEarlyClobber, OutputRegs, InputRegs); Assuming the correct fix is to enhance llvm::TargetLowering::getRegForInlineAsmConstraint(), can someone give me some pointers as to how to fix it? I have no experience with the code and like to get my hands dirty... Thanks, BTW: Is there a cross-reference of the project somewhere? -- Ma...