search for: data16

...y** @my_value .... } After that, I use the following command: bash$ llc -relocation-model=pic test.ll And I have test.s which is an assembly file. I tried to build it with gcc, but I have the following warning bash$ gcc -c test.s test.s: Assembler messages: test.s:43: Warning: stand-alone `data16' prefix I just wonder why I have data16 instruction in my assembly file. (ps. If I build it with "llc test.ll", the assembly file will not have data16 instruction) I search the llvm project and find some clues in this file: lib/Target/X86/X86MCInstLower.cpp static void LowerTlsAddr(...

Hey Cameron, Sorry to reply this mail so late. Recently, I tried to understand what's the impact of the warning message (Warning: stand-alone `data16' prefix) And in binutils (gas/config/tc-i386.c), I found: if (!quiet_warnings) { ..... if (t->opcode_modifier.isprefix && t->opcode_modifier.ignoresize) { /* Warn them that a data or address size prefix doesn't affect assembly of the n...

...lustr-03:/mnt/data11 clustr-01:/mnt/data12 clustr-02:/mnt/data12 clustr-03:/mnt/data12 clustr-01:/mnt/data13 clustr-02:/mnt/data13 clustr-03:/mnt/data13 clustr-01:/mnt/data14 clustr-02:/mnt/data14 clustr-03:/mnt/data14 clustr-01:/mnt/data15 clustr-02:/mnt/data15 clustr-03:/mnt/data15 clustr-01:/mnt/data16 clustr-02:/mnt/data16 clustr-03:/mnt/data16 clustr-01:/mnt/data17 clustr-02:/mnt/data17 clustr-03:/mnt/data17 clustr-01:/mnt/data18 clustr-02:/mnt/data18 clustr-03:/mnt/data18 clustr-01:/mnt/data19 clustr-02:/mnt/data19 clustr-03:/mnt/data19 clustr-01:/mnt/data20 clustr-02:/mnt/data20 clustr-03:/mn...

Hi, Martin Str|mberg wrote: > And given that space in isohdpfx is very limited (432 bytes) perhaps > the right thing might be to not have that xor in there. > But then better safe than sorry, and given that there is space _now_, > why not? I still agree. But while answering Ady's questions i get to a question of my own: Do all six fixed isohdp*.bin variations still fit into 432

...54 push %r12 5e59: 53 push %rbx 5e5a: 48 83 ec 58 sub $0x58,%rsp 5e5e: 31 db xor %ebx,%ebx 5e60: 45 31 f6 xor %r14d,%r14d 5e63: 66 66 66 66 2e 0f 1f data16 data16 data16 nopw %cs:0x0(%rax,%rax,1) 5e6a: 84 00 00 00 00 00 5e70: 4c 89 34 24 mov %r14,(%rsp) 5e74: 48 89 5c 24 08 mov %rbx,0x8(%rsp) 5e79: 4c 8b 3c 24 mov (%rsp),%r15 5e7d: 48 8b 04 24 mov...

...31 <__FUNCTION__.21806+0x11> > - 4d2: 72 65 jb 539 <__FUNCTION__.21806+0x19> > + 4d0: 74 5f je 531 <__FUNCTION__.21719+0x11> > + 4d2: 72 65 jb 539 <__FUNCTION__.21719+0x19> > 4d4: 66 data16 > ... > > -000004e0 <__FUNCTION__.21966>: > +000004e0 <__FUNCTION__.21879>: > 4e0: 61 popa > 4e1: 64 fs > 4e2: 6a 75 push $0x75 > - 4e4: 73 74 jae 55a <__FUNCTION__.22434+0x6&gt...

...im("t (12).txt", quote="", as.is=TRUE) data13 <-read.delim("t (13).txt", quote="", as.is=TRUE) data14 <-read.delim("t (14).txt", quote="", as.is=TRUE) data15 <-read.delim("t (15).txt", quote="", as.is=TRUE) data16 <-read.delim("t (16).txt", quote="", as.is=TRUE) data17 <-read.delim("t (17).txt", quote="", as.is=TRUE) data18 <-read.delim("t (18).txt", quote="", as.is=TRUE) data19 <-read.delim("t (19).txt", quote="",...

The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the

...d780 0000060010fac140 0000030004e52240 000002a100a67950 zfs:txg_sync_thread+248 (60010fac140, 7, 7b2fac0b, 5bad, 60010fac258, bb8) %l0-3: 0000060010fac2a0 0000060010fac2a6 0000060010fac2a4 00000000018d7e28 %l4-7: 00000000700b4a64 0000000000000007 0000000000000003 000000007b30c6e0 Test machine: data16.sfbay Core files: /var/crash/data16/*.11 Test case zfs_create_005 causes system panic. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN

...) - ABSOLUTE(__bcopyxx_data_start)); - HIDDEN(__bcopyxx_data_dwords = (__bcopyxx_data_len + 3) >> 2); - - HIDDEN(__bcopyxx_end = .); - HIDDEN(__bcopyxx_len = ABSOLUTE(__bcopyxx_end) - ABSOLUTE(__bcopyxx_start)); - HIDDEN(__bcopyxx_dwords = (__bcopyxx_len + 3) >> 2); - - . = ALIGN(4); - .data16 : { - HIDDEN(__data16_start = .); - *(.data16) - HIDDEN(__data16_end = .); - } - HIDDEN(__data16_len = ABSOLUTE(__data16_end) - ABSOLUTE(__data16_start)); - HIDDEN(__data16_dwords = (__data16_len + 3) >> 2); - - . = ALIGN(4); - HIDDEN(__config_lma = .); - . += SIZEOF(.config); - - . = ALIG...

...+ 792:; +#define vmi_padded_begin 791b +#define vmi_padded_end 792b +#define vmi_padded_len (vmi_padded_end - vmi_padded_begin) + +#define vmi_call(name) \ + call .+5+name + +/* + * Pad out the current native instruction sequence with a series of nops; + * the nop used is 0x66* 0x90 which is data16 nop or xchg %ax, %ax. We + * pad out with up to 11 bytes of prefix at a time because beyond that + * both AMD and Intel processors start to show inefficiencies. + */ +#define vmi_nop_pad \ +.equ vmi_pad_total, vmi_translation_len - vmi_native_len; \ +.equ vmi_pad, vmi_pad_total; \ +.rept...

...+ 792:; +#define vmi_padded_begin 791b +#define vmi_padded_end 792b +#define vmi_padded_len (vmi_padded_end - vmi_padded_begin) + +#define vmi_call(name) \ + call .+5+name + +/* + * Pad out the current native instruction sequence with a series of nops; + * the nop used is 0x66* 0x90 which is data16 nop or xchg %ax, %ax. We + * pad out with up to 11 bytes of prefix at a time because beyond that + * both AMD and Intel processors start to show inefficiencies. + */ +#define vmi_nop_pad \ +.equ vmi_pad_total, vmi_translation_len - vmi_native_len; \ +.equ vmi_pad, vmi_pad_total; \ +.rept...

...i/blib.a(librm.o): In function `real_to_prot': (.text16.real_to_prot+0x33): relocation truncated to fit: R_X86_64_16 against `.bss16.rm_virt_addrs' bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot': (.text16.real_to_prot+0x39): relocation truncated to fit: R_X86_64_16 against `.data16.gdt' bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot': (.text16.real_to_prot+0x58): relocation truncated to fit: R_X86_64_32 against `.text.real_to_prot' bin-x86_64-efi/blib.a(librm.o): In function `r2p_pmode': (.text.real_to_prot+0x10): relocation truncated to fit: R_X86_...

...8a: eb fe jmp 8a <_start+0x7a> 8c: eb 00 jmp 8e <_start+0x7e> 8e: 48 83 c4 40 add $0x40,%rsp 92: 5d pop %rbp 93: c3 retq 94: 66 66 66 2e 0f 1f 84 data16 data16 nopw %cs:0x0(%rax,%rax,1) 9b: 00 00 00 00 00 00000000000000a0 <__udivti3>: a0: 55 push %rbp a1: 48 89 e5 mov %rsp,%rbp a4: 48 89 7d f0 mov %rdi,-0x10(%rbp) a8: 48 89 75 f8 mov %rsi,-0x8...

...jmp 8a <_start+0x7a> > 8c: eb 00 jmp 8e <_start+0x7e> > 8e: 48 83 c4 40 add $0x40,%rsp > 92: 5d pop %rbp > 93: c3 retq > 94: 66 66 66 2e 0f 1f 84 data16 data16 nopw %cs:0x0(%rax,%rax,1) > 9b: 00 00 00 00 00 > > 00000000000000a0 <__udivti3>: > a0: 55 push %rbp > a1: 48 89 e5 mov %rsp,%rbp > a4: 48 89 7d f0 mov %rdi,-0x10(%rbp) > a8: 48 89 7...

...start+0x7a> > > 8c: eb 00 jmp 8e <_start+0x7e> > > 8e: 48 83 c4 40 add $0x40,%rsp > > 92: 5d pop %rbp > > 93: c3 retq > > 94: 66 66 66 2e 0f 1f 84 data16 data16 nopw %cs:0x0(%rax,%rax,1) > > 9b: 00 00 00 00 00 > > > > 00000000000000a0 <__udivti3>: > > a0: 55 push %rbp > > a1: 48 89 e5 mov %rsp,%rbp > > a4: 48 89 7d f0 mov %rdi,-0x...

...smith (6): specs/libX11: More synopsis fixes specs/libX11: Fix paramdef entries listing multiple parameters specs/libX11: Make paramdef spacing more consistent specs/libX11: Add missing parameter types for XGetWindowProperty() specs/libX11: Fix broken synopsis for Data/Data16/Data32 specs/libX11: Update Portability Considerations for the 21st century Emil Velikov (1): autogen.sh: use quoted string variables Emilio Pozuelo Monfort (1): Plug a memory leak Julien Cristau (1): Fix wrong Xfree in XListFonts failure path Lucien Gentis (1): Ty...

...can look at the resulting .lst files to see what values the instructions turned into (except for values that are determined at link time). Also you should immediately see the offset that you want to patch instead of needing to search. Another good command is "objdump -D -b binary -m i8086 -M data16,addr16 isohdpfx.bin" if you want to see the assembly code of something compiled for barebones 16-bit x86. -- MartinS

...dsk/bug/devices/data18 /dev/zvol/rdsk/bug/devices/data86 .. .. .. /dev/zvol/rdsk/bug/devices/data149 /dev/zvol/rdsk/bug/devices/data82 /dev/zvol/rdsk/bug/devices/log49 /dev/zvol/rdsk/bug/devices/data15 /dev/zvol/rdsk/bug/devices/data83 /dev/zvol/rdsk/bug/devices/master /dev/zvol/rdsk/bug/devices/data16 /dev/zvol/rdsk/bug/devices/data84 /dev/zvol/rdsk/bug/devices/sysproc