ObjFW  History of src/runtime/lookup-asm/lookup-asm-x86-win32.S of merge-in:b1eae58

This only uses endbr32/endbr64 when actually needed and emits the
necessary .note.gnu.property. file: [447b9d83b0] check-in: [de552578e7] user: js, branch: 1.0, size: 2016 [annotate] [blame] [check-ins using] [diff]

This only uses endbr32/endbr64 when actually needed and emits the
necessary .note.gnu.property. file: [31732be2f7] check-in: [0b441e52d6] user: js, branch: trunk, size: 2026 [annotate] [blame] [check-ins using] [diff]

Support for the Intel syntax is too buggy in toolchains to be usable. file: [15ce3f96a4] check-in: [14d5bc2bbc] user: js, branch: trunk, size: 1930 [annotate] [blame] [check-ins using] [diff]

This used to be in Intel syntax, but was moved back to AT&T syntax for
consistency with the Mach-O version, where the assembler doesn't support
the Intel syntax properly. However, it makes more sense to use Intel
syntax where possible. file: [045420d8bf] check-in: [357bcde965] user: js, branch: trunk, size: 1982 [annotate] [blame] [check-ins using] [diff]

This is for consistency with the Mach-O version. file: [7e33d5be64] check-in: [603524c162] user: js, branch: trunk, size: 1840 [annotate] [blame] [check-ins using] [diff]

This leaves 28/60 bits for the value. file: [6bf3eb314e] check-in: [943cf97843] user: js, branch: tagged-pointers, size: 1942 [annotate] [blame] [check-ins using] [diff]

GAS has decent support for Intel syntax these days, so there is little
reason to stick with AT&T syntax. file: [44cfb2c923] check-in: [2630b77909] user: js, branch: trunk, size: 1738 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [eb2fd9ea14] check-in: [44f45c2e35] user: js, branch: trunk, size: 1768 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [9c647421e1] check-in: [2a27cf3000] user: js, branch: trunk, size: 1725 [annotate] [blame] [check-ins using] [diff]

It matches the Apple API and ABI now and the forwarding handler itself
determines whether it should forward or not.

This moves handling of +[resolve{Class,Instance}Method:] to the runtime
and allows adding new kinds of forwarding without changing the runtime.

Also fixes a potential stack problem in the forwarding for MIPS. file: [a61203a836] check-in: [0c332aa2d2] user: js, branch: trunk, size: 1766 [annotate] [blame] [check-ins using] [diff]