From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DE66B3858D20; Wed, 27 Mar 2024 17:42:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DE66B3858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1711561337; bh=qmnLIeo/NNh0q6tKpLcsias8XUB6gRwynqSOHzsRefo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sJ1q03UdhkYNU7XBIXYNiIBIoesAThRQMhmc6e704tlWqskp0w/gcW3NJjGQzhvqW 2KOfhlsUGNa4Ltuq7Dvlvjf+O2xXwnmCJtSaAiYMAbh94J9rclGWJT4AnCErruY0qW aDpIccFRsHeKxFjmrMjMgfUgEPgAtezdwoZ8YwoU= From: "dimula73 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows Date: Wed, 27 Mar 2024 17:42:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.7.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: dimula73 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D54412 --- Comment #42 from Dmitry Kazakov --- Hi, Avraham! > Does it remain true that the only option to get around this bug without k= illing all AVX2 is to pass "-Wa,-muse-unaligned-vector-move" when compiling= using GCC on Windows 64? Thank you I'm not sure about your particular issue, but in our case we used to manage= to workaround this issue by passing AVX2-related structures by reference (or const-reference, when possible).=