public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Cc: Matthew Glazar <strager.nds@gmail.com>,
	Jan Beulich <jbeulich@suse.com>,
	Dave Korn <dave.korn.cygwin@gmail.com>
Subject: PR29189, dlltool delaylibs corrupt float/double arguments
Date: Wed, 17 May 2023 10:22:55 +0930	[thread overview]
Message-ID: <ZGQlZ4KofqcYiJX1@squeak.grove.modra.org> (raw)

PR29189 is an excellent bug report.  The reporter debugged the problem
to the point of finding out exactly where things were going wrong (in
a windows dll, so not a mingw problem) and even supplied a fix, giving
an ABI reference.  There hasn't been any action on the bug report due
to lack of an active mingw binutils maintainer, so I thought I'd take
a look as part of trying to whittle down the enormous number of
binutils bugzilla entries.

This is a rewrite of the patch given in the PR.  (It might even
resemble code emitted by Microsoft's LINK.EXE as reported in
https://www.mail-archive.com/llvm-bugs@lists.llvm.org/msg55205.html).
I'm not going to apply it without review from an x86 maintainer,
because it's been too long since I did any serious x86 specific work
and I don't want to break things for someone running an original amd64
machine.  The patch needs to be tested too.  I don't have a mingw
setup.

	PR 29189
	* dlltool.c (i386_x64_trampoline): Save and restore xmm0-3.  Make
	use of parameter save area for integer arg regs.  Comment.

diff --git a/binutils/dlltool.c b/binutils/dlltool.c
index 31c864d7d5c..eb2c4f34658 100644
--- a/binutils/dlltool.c
+++ b/binutils/dlltool.c
@@ -583,22 +583,37 @@ static const char i386_trampoline[] =
   "\tpopl %%ecx\n"
   "\tjmp *%%eax\n";
 
+/* Save integer arg regs in parameter space reserved by our caller
+   above the return address.  Allocate space for four fp arg regs plus
+   parameter space possibly used by __delayLoadHelper2 plus alignment.
+   We enter with the stack offset from 16-byte alignment by the return
+   address, so allocate 64 + 32 + 8 = 104 bytes.
+   FIXME: do we need to save avx ymm0-5 used to pass vectors args?  If
+   so, how to do it without blowing up on cpus without avx, cpuid?  */
 static const char i386_x64_trampoline[] =
-  "\tsubq $72, %%rsp\n"
-  "\t.seh_stackalloc 72\n"
+  "\tsubq $104, %%rsp\n"
+  "\t.seh_stackalloc 104\n"
   "\t.seh_endprologue\n"
-  "\tmovq %%rcx, 64(%%rsp)\n"
-  "\tmovq %%rdx, 56(%%rsp)\n"
-  "\tmovq %%r8, 48(%%rsp)\n"
-  "\tmovq %%r9, 40(%%rsp)\n"
-  "\tmovq  %%rax, %%rdx\n"
-  "\tleaq  __DELAY_IMPORT_DESCRIPTOR_%s(%%rip), %%rcx\n"
+  "\tmovq %%rcx, 104+8(%%rsp)\n"
+  "\tmovq %%rdx, 104+16(%%rsp)\n"
+  "\tmovq %%r8, 104+24(%%rsp)\n"
+  "\tmovq %%r9, 104+32(%%rsp)\n"
+  "\tmovaps %%xmm0, 32(%%rsp)\n"
+  "\tmovaps %%xmm1, 48(%%rsp)\n"
+  "\tmovaps %%xmm2, 64(%%rsp)\n"
+  "\tmovaps %%xmm3, 80(%%rsp)\n"
+  "\tmovq %%rax, %%rdx\n"
+  "\tleaq __DELAY_IMPORT_DESCRIPTOR_%s(%%rip), %%rcx\n"
   "\tcall __delayLoadHelper2\n"
-  "\tmovq 40(%%rsp), %%r9\n"
-  "\tmovq 48(%%rsp), %%r8\n"
-  "\tmovq 56(%%rsp), %%rdx\n"
-  "\tmovq 64(%%rsp), %%rcx\n"
-  "\taddq $72, %%rsp\n"
+  "\tmovq 104+8(%%rsp), %%rcx\n"
+  "\tmovq 104+16(%%rsp), %%rdx\n"
+  "\tmovq 104+24(%%rsp), %%r8\n"
+  "\tmovq 104+32(%%rsp), %%r9\n"
+  "\tmovaps 32(%%rsp), %%xmm0\n"
+  "\tmovaps 48(%%rsp), %%xmm1\n"
+  "\tmovaps 64(%%rsp), %%xmm2\n"
+  "\tmovaps 80(%%rsp), %%xmm3\n"
+  "\taddq $104, %%rsp\n"
   "\tjmp *%%rax\n";
 
 struct mac

-- 
Alan Modra
Australia Development Lab, IBM

             reply	other threads:[~2023-05-17  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  0:52 Alan Modra [this message]
2023-05-17 10:18 ` Jan Beulich
2023-05-17 23:52   ` Alan Modra
2023-05-19  7:11     ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZGQlZ4KofqcYiJX1@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=dave.korn.cygwin@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=strager.nds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).