search for: 11f

...movss 0xc(%rsp),%xmm0 106: e8 00 00 00 00 callq 10b <_Z4fct3Pf+0x2b> 10b: c5 fa 11 43 04 vmovss %xmm0,0x4(%rbx) 110: c5 fa 10 43 08 vmovss 0x8(%rbx),%xmm0 115: e8 00 00 00 00 callq 11a <_Z4fct3Pf+0x3a> 11a: c5 fa 11 43 08 vmovss %xmm0,0x8(%rbx) 11f: c5 fa 10 43 0c vmovss 0xc(%rbx),%xmm0 124: e8 00 00 00 00 callq 129 <_Z4fct3Pf+0x49> 129: c5 fa 11 43 0c vmovss %xmm0,0xc(%rbx) 12e: c5 fa 10 43 10 vmovss 0x10(%rbx),%xmm0 133: e8 00 00 00 00 callq 138 <_Z4fct3Pf+0x58> 138: c5 fa 11 43 10...

Hi, Given two disk c1t0d0 (DISK A) and c1t1d0 (DISK B)... 1/ Standard install on DISK A. 2/ zfs boot install on DISK B. 3/ I change the boot order and my zfs boot works fine. 4/ I install grub on the mbr of DISK B 5/ I disconnect and replace DISK A with DISK B 6/ Reboot, get the grub menu select Solaris ZFS and it panics that it cannot mount root path @ device XXX... This is not a ZFS

On Fri, Oct 19, 2012 at 2:55 AM, r4start <r4start at gmail.com> wrote: > Hi all. > > While compiling next code > @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, > section ".data" > was discovered that llc ignores weak linkage if we emit it in COFF object. > Attached patch solves this problem, please review. > > I found some

...d/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 11c [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 11d [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 11e [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 11f [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 120 [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 121 [2002/03/05 14:20:24, 1] smbd/ipc.c:(292) api_fd_reply: INVALID PIPE HANDLE: 122 Any ideas? Regards Russell -- Network and Sys...

Hi all. While compiling next code @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, section ".data" was discovered that llc ignores weak linkage if we emit it in COFF object. Attached patch solves this problem, please review. I found some similar tests in test/Objects/Inputs. Should I do something like trivial.ll checking or there is a better way to check

...F 66 74 20 28 52 29 20 ..Microsoft (R) 00000050: 4F 70 74 69 6D 69 7A 69 6E 67 20 43 6F 6D 70 69 Optimizing Compi 00000060: 6C 65 72 00 ler. SECTION HEADER #3 .xdata name 0 physical address 0 virtual address 4 size of raw data 11F file pointer to raw data (0000011F to 00000122) 0 file pointer to relocation table 0 file pointer to line numbers 0 number of relocations 0 number of line numbers C0301040 flags Initialized Data COMDAT; sym= _aaa 4 byte align Read Writ...

# Summary As a consequence of comparing the RISC-V LLVM MC assembler to the RISC-V GNU assembler I've noticed that a number of targets have quite different handling for pc-relative jumps/branches with immediate integer operands in llvm-mc vs GNU as. I'll admit that this isn't likely to occur in hand-written code (as you'd almost always prefer to use a label), but thought it was

Hi Linus, This is a huge set of several partly interrelated (and concurrently developed) changes, which is why the branch history is messier than one would like. The *really* big items are two humonguous patchsets mostly developed by Yinghai Lu at my request, which completely revamps the way we create initial page tables. In particular, rather than estimating how much memory we will need for

Hi Linus, This is a huge set of several partly interrelated (and concurrently developed) changes, which is why the branch history is messier than one would like. The *really* big items are two humonguous patchsets mostly developed by Yinghai Lu at my request, which completely revamps the way we create initial page tables. In particular, rather than estimating how much memory we will need for

Hi Linus, This is a huge set of several partly interrelated (and concurrently developed) changes, which is why the branch history is messier than one would like. The *really* big items are two humonguous patchsets mostly developed by Yinghai Lu at my request, which completely revamps the way we create initial page tables. In particular, rather than estimating how much memory we will need for

...tion +start_hyper_text: + +.global host_syscall +host_syscall: + .quad 0 + +#define PRINT_L(L) \ + PRINT_OUT($L) + +#define PRINT_N(n) \ + PRINT_OUT($'0' + $n) + +#define PRINT_HEX(n) \ + mov n, %cl; \ + and $0xf, %cl; \ + cmp $0xa, %cl; \ + jge 11f; \ + add $'0', %cl; \ + jmp 12f; \ +11: add $('a' - 10), %cl; \ +12: PRINT_OUT(%cl); + +#define PRINT_NUM_BX \ +9: PRINT_HEX(%bl); \ + shr $4, %rbx; \ + jne 9b + +#define PRINT_NUM(n) \ + movl $n, %ebx; \ + PRINT_NUM_BX; \...

...tion +start_hyper_text: + +.global host_syscall +host_syscall: + .quad 0 + +#define PRINT_L(L) \ + PRINT_OUT($L) + +#define PRINT_N(n) \ + PRINT_OUT($'0' + $n) + +#define PRINT_HEX(n) \ + mov n, %cl; \ + and $0xf, %cl; \ + cmp $0xa, %cl; \ + jge 11f; \ + add $'0', %cl; \ + jmp 12f; \ +11: add $('a' - 10), %cl; \ +12: PRINT_OUT(%cl); + +#define PRINT_NUM_BX \ +9: PRINT_HEX(%bl); \ + shr $4, %rbx; \ + jne 9b + +#define PRINT_NUM(n) \ + movl $n, %ebx; \ + PRINT_NUM_BX; \...

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths