public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49001] GCC uses VMOVAPS/PD AVX instructions to access stack variables that are not 32-byte aligned
Date: Sun, 15 May 2011 21:27:00 -0000 [thread overview]
Message-ID: <bug-49001-4-CsmF5CrxYL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49001-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49001
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktietz at gcc dot gnu.org
Severity|critical |normal
--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2011-05-15 18:49:44 UTC ---
(In reply to comment #0)
> I'm using a custom mingw64 build of GCC 4.6.1. My target is Windows 64bit. I
> compile with g++ -03 -march=corei7-avx -mtune=corei7-avx -mavx.
Please provide testcase that can be compiled without changes. See [1].
FWIW, I have tested following testcase on x86_64-pc-linux-gnu:
--cut here--
#include <x86intrin.h>
__m256 sin256_ps_avx (__m256);
__m256 dummy_ps256;
void test_stackalign32() {
volatile __m256 x = dummy_ps256;
dummy_ps256 = sin256_ps_avx(x);
}
--cut here--
And got expected code (gcc-4.6.1):
test_stackalign32:
.LFB828:
.cfi_startproc
pushq %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp
.cfi_def_cfa_register 6
andq $-32, %rsp
subq $32, %rsp
vmovaps dummy_ps256(%rip), %ymm0
vmovaps %ymm0, (%rsp)
vmovaps (%rsp), %ymm0
call sin256_ps_avx
vmovaps %ymm0, dummy_ps256(%rip)
leave
.cfi_def_cfa 7, 8
vzeroupper
ret
Probably mingw64 specific problem... CC added.
[1] http://gcc.gnu.org/bugs/#report
next prev parent reply other threads:[~2011-05-15 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 21:01 [Bug target/49001] New: " npozar at quick dot cz
2011-05-14 20:48 ` [Bug target/49001] " npozar at quick dot cz
2011-05-15 21:27 ` ubizjak at gmail dot com [this message]
2011-05-15 22:26 ` hjl.tools at gmail dot com
2011-05-16 7:22 ` npozar at quick dot cz
2014-09-03 21:18 ` roland at rschulz dot eu
2021-08-22 18:35 ` arthur200126 at gmail dot com
2021-08-22 18:39 ` arthur200126 at gmail dot com
2021-12-21 12:35 ` thiago at kde dot org
2024-02-19 17:00 ` pinskia 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-49001-4-CsmF5CrxYL@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).