public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rcopley at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54412] Request for 32-byte stack alignment with -mavx on Windows
Date: Sun, 21 Sep 2014 01:08:00 -0000 [thread overview]
Message-ID: <bug-54412-4-8XmwHz0ySU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54412-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #11 from R Copley <rcopley at gmail dot com> ---
On 20 September 2014 07:08, roland at rschulz dot eu
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
>
> --- Comment #10 from Roland Schulz <roland at rschulz dot eu> ---
> Created attachment 33520
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33520&action=edit
> Slightly modified testcase
>
> This slightly modified testcase in which the return value isn't stored, still
> segfaults for me. With the 32bit mingw64 binary ((i686-win32-dwarf-rev1, Built
> by MinGW-W64 project) 4.9.1) it is OK, but with the 64bit binary
> ((x86_64-win32-seh-rev1, Built by MinGW-W64 project) 4.9.1) it segfaults.
Confirmed (with the same compiler, in the mingw-builds toolchain). I
compiled your testcase with command "gcc -O0 -g -ggdb -m64 -mavx
bug.c". It segfaults on the instruction marked "=>" below.
(gdb) disassemble /m
Dump of assembler code for function f:
6 {
0x00000000004014f0 <+0>: push %rbp
0x00000000004014f1 <+1>: mov %rsp,%rbp
0x00000000004014f4 <+4>: mov %rcx,0x10(%rbp)
0x00000000004014f8 <+8>: sub $0x40,%rsp
0x00000000004014fc <+12>: mov %rsp,%rax
0x00000000004014ff <+15>: add $0x1f,%rax
0x0000000000401503 <+19>: shr $0x5,%rax
0x0000000000401507 <+23>: shl $0x5,%rax
7 v4d x __attribute__ ((aligned (32))) = { 1.0, 2.0, 3.0, 4.0, };
0x000000000040150b <+27>: vmovapd 0x2aed(%rip),%ymm0 # 0x404000
0x0000000000401513 <+35>: vmovapd %ymm0,(%rax)
8 return x;
0x0000000000401517 <+39>: mov 0x10(%rbp),%rdx
0x000000000040151b <+43>: vmovapd (%rax),%ymm0
=> 0x000000000040151f <+47>: vmovapd %ymm0,(%rdx)
9 }
0x0000000000401523 <+51>: mov 0x10(%rbp),%rax
0x0000000000401527 <+55>: mov %rbp,%rsp
0x000000000040152a <+58>: pop %rbp
0x000000000040152b <+59>: retq
End of assembler dump.
(gdb) print $rdx % 32
$1 = 16
next prev parent reply other threads:[~2014-09-21 1:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 1:10 [Bug target/54412] New: " rcopley at gmail dot com
2013-09-10 10:30 ` [Bug target/54412] " ktietz at gcc dot gnu.org
2013-09-10 17:26 ` rcopley at gmail dot com
2013-09-10 17:49 ` rcopley at gmail dot com
2014-09-03 21:17 ` roland at rschulz dot eu
2014-09-04 22:49 ` rcopley at gmail dot com
2014-09-05 1:42 ` roland at rschulz dot eu
2014-09-05 18:40 ` rcopley at gmail dot com
2014-09-05 18:44 ` rcopley at gmail dot com
2014-09-21 1:08 ` rcopley at gmail dot com [this message]
2015-09-22 10:51 ` ktietz at gcc dot gnu.org
2021-08-23 3:12 ` [Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows arthur200126 at gmail dot com
2021-08-25 5:38 ` dimula73 at gmail dot com
2021-09-26 7:15 ` mehdi.chinoune at hotmail dot com
2022-04-01 15:01 ` lists at coryfields dot com
2022-04-01 15:38 ` ebotcazou at gcc dot gnu.org
2022-04-01 16:27 ` steve at sk2 dot org
2022-04-01 17:59 ` jakub at gcc dot gnu.org
2022-04-01 20:25 ` ebotcazou at gcc dot gnu.org
2022-04-01 20:50 ` rcopley at gmail dot com
2022-04-01 21:00 ` ebotcazou at gcc dot gnu.org
2022-04-20 14:41 ` hjl.tools at gmail dot com
2024-01-09 10:15 ` ebotcazou at gcc dot gnu.org
2024-03-26 15:12 ` avraham.adler at gmail dot com
2024-03-27 17:42 ` dimula73 at gmail dot com
2024-03-28 17:30 ` avraham.adler at gmail dot com
2024-03-28 20:26 ` ebotcazou at gcc dot gnu.org
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=bug-54412-4-8XmwHz0ySU@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).