openbsd/src/lib/libcrypto/aes/asm, branch OPENBSD_7_3_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_3_BASE 2023-02-23T08:55:44+00:00 Use explicit .text instead of .previous to please Windows/MinGW on amd64 2023-02-23T08:55:44+00:00 tb 2023-02-23T08:55:44+00:00 urn:sha1:0dadd2bf46f37ca96a50e247649a11b3c5273234 ok miod Use .section .rodata instead of a plain .rodata 2023-02-09T19:57:00+00:00 tb 2023-02-09T19:57:00+00:00 urn:sha1:4355eb6aeababf0126972f85bdeed63048a99df1 At least gcc 12 on Fedora is very unhappy about a plain .rodata and throws Error: unknown pseudo-op: `.rodata'. So add a .section in front of it to make it happy. ok deraadt miod Remove AIX toc data after every function. NFC 2023-02-02T20:12:05+00:00 miod 2023-02-02T20:12:05+00:00 urn:sha1:236a5d2198d194578e1ab95b61039a767942692a Unbreak vpaes-x86 implementation. 2023-02-02T18:19:27+00:00 jsing 2023-02-02T18:19:27+00:00 urn:sha1:b038ca2d2e8fa273b344804a2561d8aad704bdcc Remove remnants of previous PIC handling. ok miod@ Move all data blocks from .text to .rodata and cleanup up and homogeneize code 2023-02-01T20:45:04+00:00 miod 2023-02-01T20:45:04+00:00 urn:sha1:5957c398bf683b5334ed18dd0f830b1cfffbf027 responsible from getting the proper address of those blocks. ok tb@ jsing@ Move constants out of text segment into rodata to prepare for xonly support 2023-01-14T16:58:56+00:00 deraadt 2023-01-14T16:58:56+00:00 urn:sha1:eb72d17d580445c364a2dfb2d637026a00e779eb on amd64. no pic handling is neccessary since amd64 has full reach. ok kettenis Move all data tables from .text section to .rodata, and update the code to 2023-01-13T17:27:26+00:00 miod 2023-01-13T17:27:26+00:00 urn:sha1:25c59400a04e7301aaa6acb604b5ebef9d2f4cf1 fetch them correctly when building PIC. Also drop unused data, and remove --no-execute-only from linker flags. ok kettenis@ Move all data tables from .text section to .rodata, and update the code to 2023-01-13T17:11:41+00:00 miod 2023-01-13T17:11:41+00:00 urn:sha1:6f56f28c72618c1e8d79d943e58f0f1c66e73832 fetch them correctly when building PIC. Also drop unused data, and remove --no-execute-only from linker flags. ok jsing@ kettenis@ spelling fixes; from paul tagliamonte 2022-12-26T07:18:53+00:00 jmc 2022-12-26T07:18:53+00:00 urn:sha1:2eb7e5ff6bb69760f9dd4a43e7e3520ebb930120 i removed the arithmetics -> arithmetic changes, as i felt they were not clearly correct ok tb Add stack frames to AES-NI x86_64 assembly. 2022-07-30T13:51:31+00:00 jsing 2022-07-30T13:51:31+00:00 urn:sha1:30f1a78757d14295127ac8f3bff0c411fc8a0911 The current AES-NI x86_64 assembly does some strange, although valid things, such as making internal function calls without creating stack frames. In this case, the return address lands in the red zone (which it allows for when making use of the stack) and everything works as expected. However, this trips a false positive in valgrind, which seems to think that any data saved on the stack prior to the internal function call is now "undefined" once the function returns. Avoid this by actually using stack frames - this brings in most of 6a40ebe86b4 from OpenSSL, omitting the unnecessary explicit stack alignment (which was apparently added so this code could be used in the Linux kernel with an incorrectly aligned stack). Valgrind issue reported by Steffen Jaeckel (@sjaeckel), found via libstrophe unit tests. ok tb@