HomeSort by relevance Sort by last modified time
    Searched full:hi16s (Results 1 - 6 of 6) sorted by null

  /toolchain/binutils/binutils-2.27/bfd/
elf32-v850.c 213 entry, then we know that the hi16s reloc has already been updated
306 HI16S reloc. So for example, these relocations:
341 clear, the assembler will not have added 1 to the previous HI16S reloc
347 The value stored in HI16S reloc is 0x12, the value stored in the LO16
351 HI16S: 0x0012 + (0x00007000 >> 16) = 0x12
368 HI16S: 0x0011 + (0x00007000 >> 16) = 0x11
378 bit of the original value. What happens is that the HI16S reloc
389 HI16S: 0x0001 + (0x0000f000 >> 16) = 0x0001
403 HI16S: 0x0000 + (0x0000f000 >> 16) = 0x0000
412 15th bit changes its value from being set to being clear, as the HI16S
    [all...]
elf32-mep.c 127 MAP(HI16S);
ChangeLog-9899     [all...]
elfxx-mips.c     [all...]
  /external/valgrind/VEX/priv/
host_amd64_isel.c 1290 HReg hi16s = iselIntExpr_R(env, e->Iex.Binop.arg1); local
    [all...]
host_x86_isel.c 1065 HReg hi16s = iselIntExpr_R(env, e->Iex.Binop.arg1); local
    [all...]

Completed in 132 milliseconds