kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
9b1cfd9893
boringssl/util/fipstools/delocate/testdata/x86_64-GOTRewrite/out.s

266 lines
5.2 KiB
ArmAsm
Raw Normal View History

Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
.text
delocate: put emitted labels in a specific file. Otherwise Clang has to assign a file entry to the label which conflicts with later, explicit, file entries. Change-Id: Ifc782821517aa7b48ba3ef304d4468f2bc850ac2 Reviewed-on: https://boringssl-review.googlesource.com/27544 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-04-19 17:05:03 +01:00
.file 1 "inserted_by_delocate.c"
.loc 1 1 0
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
BORINGSSL_bcm_text_start:
.text
.Lfoo_local_target:
foo:
# leaq of OPENSSL_ia32cap_P is supported.
# WAS leaq OPENSSL_ia32cap_P(%rip), %r11
Update delocate to handle new compiler output. Delocate failed with some versions of Clang that reference OPENSSL_ia32cap_P with an orq instruction. Change-Id: I448d291594f5f147424e6f7014a681c4201b0aee Reviewed-on: https://boringssl-review.googlesource.com/29764 Reviewed-by: Adam Langley <alangley@gmail.com>
2018-07-13 19:47:46 +01:00
leaq -128(%rsp), %rsp
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
pushfq
leaq OPENSSL_ia32cap_addr_delta(%rip), %r11
addq (%r11), %r11
popfq
Update delocate to handle new compiler output. Delocate failed with some versions of Clang that reference OPENSSL_ia32cap_P with an orq instruction. Change-Id: I448d291594f5f147424e6f7014a681c4201b0aee Reviewed-on: https://boringssl-review.googlesource.com/29764 Reviewed-by: Adam Langley <alangley@gmail.com>
2018-07-13 19:47:46 +01:00
leaq 128(%rsp), %rsp
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
# As is the equivalent GOTPCREL movq.
# WAS movq OPENSSL_ia32cap_P@GOTPCREL(%rip), %r12
Update delocate to handle new compiler output. Delocate failed with some versions of Clang that reference OPENSSL_ia32cap_P with an orq instruction. Change-Id: I448d291594f5f147424e6f7014a681c4201b0aee Reviewed-on: https://boringssl-review.googlesource.com/29764 Reviewed-by: Adam Langley <alangley@gmail.com>
2018-07-13 19:47:46 +01:00
leaq -128(%rsp), %rsp
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
pushfq
leaq OPENSSL_ia32cap_addr_delta(%rip), %r12
addq (%r12), %r12
popfq
Update delocate to handle new compiler output. Delocate failed with some versions of Clang that reference OPENSSL_ia32cap_P with an orq instruction. Change-Id: I448d291594f5f147424e6f7014a681c4201b0aee Reviewed-on: https://boringssl-review.googlesource.com/29764 Reviewed-by: Adam Langley <alangley@gmail.com>
2018-07-13 19:47:46 +01:00
leaq 128(%rsp), %rsp
# And a non-movq instruction via the GOT.
# WAS orq OPENSSL_ia32cap_P@GOTPCREL(%rip), %r12
leaq -128(%rsp), %rsp
pushq %rax
pushfq
leaq OPENSSL_ia32cap_addr_delta(%rip), %rax
addq (%rax), %rax
popfq
orq %rax, %r12
popq %rax
leaq 128(%rsp), %rsp
# ... which targets the default temp register
# WAS orq OPENSSL_ia32cap_P@GOTPCREL(%rip), %rax
leaq -128(%rsp), %rsp
pushq %rbx
pushfq
leaq OPENSSL_ia32cap_addr_delta(%rip), %rbx
addq (%rbx), %rbx
popfq
orq %rbx, %rax
popq %rbx
leaq 128(%rsp), %rsp
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
# Test that GOTPCREL accesses get translated. They are handled
# differently for local and external symbols.
# WAS pushq stderr@GOTPCREL(%rip)
pushq %rax
leaq -128(%rsp), %rsp
pushf
leaq stderr_GOTPCREL_external(%rip), %rax
addq (%rax), %rax
movq (%rax), %rax
popf
leaq 128(%rsp), %rsp
xchg %rax, (%rsp)
# WAS pushq foo@GOTPCREL(%rip)
pushq %rax
leaq .Lfoo_local_target(%rip), %rax
xchg %rax, (%rsp)
# WAS movq stderr@GOTPCREL(%rip), %r11
leaq -128(%rsp), %rsp
pushf
leaq stderr_GOTPCREL_external(%rip), %r11
addq (%r11), %r11
movq (%r11), %r11
popf
leaq 128(%rsp), %rsp
# WAS movq foo@GOTPCREL(%rip), %r11
leaq .Lfoo_local_target(%rip), %r11
# WAS vmovq stderr@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
pushf
leaq stderr_GOTPCREL_external(%rip), %rax
addq (%rax), %rax
movq (%rax), %rax
popf
delocate vmovq correctly. vmovq clears the upper 128 bits of a YMM register, while movq does not. When translating vmovq to an XMM register, we need to use vmovq in the final move in order to keep this behaviour. Change-Id: I81b6eee3ee6db0ea90d7c5098fc7c4ccefaf3b12 Reviewed-on: https://boringssl-review.googlesource.com/20424 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-09-18 17:59:52 +01:00
vmovq %rax, %xmm0
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
popq %rax
leaq 128(%rsp), %rsp
# WAS vmovq foo@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
leaq .Lfoo_local_target(%rip), %rax
delocate vmovq correctly. vmovq clears the upper 128 bits of a YMM register, while movq does not. When translating vmovq to an XMM register, we need to use vmovq in the final move in order to keep this behaviour. Change-Id: I81b6eee3ee6db0ea90d7c5098fc7c4ccefaf3b12 Reviewed-on: https://boringssl-review.googlesource.com/20424 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-09-18 17:59:52 +01:00
vmovq %rax, %xmm0
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
popq %rax
leaq 128(%rsp), %rsp
# WAS cmoveq stderr@GOTPCREL(%rip), %r11
jne 999f
leaq -128(%rsp), %rsp
pushf
leaq stderr_GOTPCREL_external(%rip), %r11
addq (%r11), %r11
movq (%r11), %r11
popf
leaq 128(%rsp), %rsp
999:
# WAS cmoveq foo@GOTPCREL(%rip), %r11
jne 999f
leaq .Lfoo_local_target(%rip), %r11
999:
# WAS cmovneq stderr@GOTPCREL(%rip), %r11
je 999f
leaq -128(%rsp), %rsp
pushf
leaq stderr_GOTPCREL_external(%rip), %r11
addq (%r11), %r11
movq (%r11), %r11
popf
leaq 128(%rsp), %rsp
999:
# WAS cmovneq foo@GOTPCREL(%rip), %r11
je 999f
leaq .Lfoo_local_target(%rip), %r11
999:
Support [v]movsd in delocate. Newer versions of LLVM can emit this instruction. Note that there are two different Intel instructions, both called “movsd”. The old one is an auto-incrementing move that doesn't take any arguments. That's not the one that is targetted in this change. Change-Id: Id0c96e0c7fe0f6e4feb8a72b5bc0fa40878225b9 Reviewed-on: https://boringssl-review.googlesource.com/20425 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-09-18 17:29:23 +01:00
# WAS movsd foo@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
leaq .Lfoo_local_target(%rip), %rax
movq %rax, %xmm0
popq %rax
leaq 128(%rsp), %rsp
# WAS vmovsd foo@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
leaq .Lfoo_local_target(%rip), %rax
vmovq %rax, %xmm0
popq %rax
leaq 128(%rsp), %rsp
Test that movsd without arguments is left as-is. This works fine, but probably worth a test. Change-Id: If060b473958c1664e450102cafe0ca28951bff49 Reviewed-on: https://boringssl-review.googlesource.com/20444 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-09-18 19:51:27 +01:00
# movsd without arguments should be left as-is.
movsd
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
# Synthesized symbols do not use the GOT.
# WAS movq BORINGSSL_bcm_text_start@GOTPCREL(%rip), %r11
leaq BORINGSSL_bcm_text_start(%rip), %r11
# WAS movq foobar_bss_get@GOTPCREL(%rip), %r11
leaq foobar_bss_get(%rip), %r11
# WAS movq OPENSSL_ia32cap_get@GOTPCREL(%rip), %r11
Move aes_nohw, bsaes, and vpaes prototypes to aes/internal.h. This is in preparation for adding ABI tests to them. In doing so, update delocate.go so that OPENSSL_ia32cap_get is consistently callable outside the module. Right now it's callable both inside and outside normally, but not in FIPS mode because the function is generated. This is needed for tests and the module to share headers that touch OPENSSL_ia32cap_P. Change-Id: Idbc7d694acfb974e0b04adac907dab621e87de62 Reviewed-on: https://boringssl-review.googlesource.com/c/34188 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com>
2019-01-06 03:49:46 +00:00
leaq .LOPENSSL_ia32cap_get_local_target(%rip), %r11
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
Support delocating vpbroadcastq. (This can be generated with -mavx2.) Change-Id: I6d92d9e93eb448357342ef86d050321f0ef40f9e Reviewed-on: https://boringssl-review.googlesource.com/24504 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-01-02 20:03:55 +00:00
# Transforming moves run the transform in-place after the load.
# WAS vpbroadcastq stderr@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
pushf
leaq stderr_GOTPCREL_external(%rip), %rax
addq (%rax), %rax
movq (%rax), %rax
popf
vmovq %rax, %xmm0
popq %rax
leaq 128(%rsp), %rsp
vpbroadcastq %xmm0, %xmm0
# WAS vpbroadcastq foo@GOTPCREL(%rip), %xmm0
leaq -128(%rsp), %rsp
pushq %rax
leaq .Lfoo_local_target(%rip), %rax
vmovq %rax, %xmm0
popq %rax
leaq 128(%rsp), %rsp
vpbroadcastq %xmm0, %xmm0
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
.comm foobar,64,32
.text
delocate: put emitted labels in a specific file. Otherwise Clang has to assign a file entry to the label which conflicts with later, explicit, file entries. Change-Id: Ifc782821517aa7b48ba3ef304d4468f2bc850ac2 Reviewed-on: https://boringssl-review.googlesource.com/27544 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-04-19 17:05:03 +01:00
.loc 1 2 0
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
BORINGSSL_bcm_text_end:
.type foobar_bss_get, @function
foobar_bss_get:
leaq foobar(%rip), %rax
ret
.type stderr_GOTPCREL_external, @object
.size stderr_GOTPCREL_external, 8
stderr_GOTPCREL_external:
.long stderr@GOTPCREL
.long 0
.type OPENSSL_ia32cap_get, @function
Move aes_nohw, bsaes, and vpaes prototypes to aes/internal.h. This is in preparation for adding ABI tests to them. In doing so, update delocate.go so that OPENSSL_ia32cap_get is consistently callable outside the module. Right now it's callable both inside and outside normally, but not in FIPS mode because the function is generated. This is needed for tests and the module to share headers that touch OPENSSL_ia32cap_P. Change-Id: Idbc7d694acfb974e0b04adac907dab621e87de62 Reviewed-on: https://boringssl-review.googlesource.com/c/34188 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com>
2019-01-06 03:49:46 +00:00
.globl OPENSSL_ia32cap_get
.LOPENSSL_ia32cap_get_local_target:
Switch to new delocate tool. Most importantly, this version of delocate works for ppc64le. It should also work for x86-64, but will need significant testing to make sure that it covers all the cases that the previous delocate.go covered. It's less stringtastic than the old code, however the parser isn't as nice as I would have liked. I thought that the reason we put up with AT&T syntax with Intel is so that assembly syntax could be somewhat consistent across platforms. At least for ppc64le, that does not appear to be the case. Change-Id: Ic7e3c6acc3803d19f2c3ff5620c5e39703d74212 Reviewed-on: https://boringssl-review.googlesource.com/16464 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-05-17 21:05:50 +01:00
OPENSSL_ia32cap_get:
leaq OPENSSL_ia32cap_P(%rip), %rax
ret
.extern OPENSSL_ia32cap_P
.type OPENSSL_ia32cap_addr_delta, @object
.size OPENSSL_ia32cap_addr_delta, 8
OPENSSL_ia32cap_addr_delta:
.quad OPENSSL_ia32cap_P-OPENSSL_ia32cap_addr_delta
.type BORINGSSL_bcm_text_hash, @object
.size BORINGSSL_bcm_text_hash, 64
BORINGSSL_bcm_text_hash:
.byte 0xae
.byte 0x2c
.byte 0xea
.byte 0x2a
.byte 0xbd
.byte 0xa6
.byte 0xf3
.byte 0xec
.byte 0x97
.byte 0x7f
.byte 0x9b
.byte 0xf6
.byte 0x94
.byte 0x9a
.byte 0xfc
.byte 0x83
.byte 0x68
.byte 0x27
.byte 0xcb
.byte 0xa0
.byte 0xa0
.byte 0x9f
.byte 0x6b
.byte 0x6f
.byte 0xde
.byte 0x52
.byte 0xcd
.byte 0xe2
.byte 0xcd
.byte 0xff
.byte 0x31
.byte 0x80
.byte 0xa2
.byte 0xd4
.byte 0xc3
.byte 0x66
.byte 0xf
.byte 0xc2
.byte 0x6a
.byte 0x7b
.byte 0xf4
.byte 0xbe
.byte 0x39
.byte 0xa2
.byte 0xd7
.byte 0x25
.byte 0xdb
.byte 0x21
.byte 0x98
.byte 0xe9
.byte 0xd5
.byte 0x53
.byte 0xbf
.byte 0x5c
.byte 0x32
.byte 0x6
.byte 0x83
.byte 0x34
.byte 0xc
.byte 0x65
.byte 0x89
.byte 0x52
.byte 0xbd
.byte 0x1f
Reference in New Issue Copy Permalink