public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106331] [12/13 Regression] Whole array assignment of empty string segfaults with -Og Date: Mon, 18 Jul 2022 08:10:38 +0000 [thread overview] Message-ID: <bug-106331-4-Po185TdtFh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106331-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106331 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code CC| |rguenth at gcc dot gnu.org Target| |x86_64-*-* --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed - we get # S.0_3 = PHI <1(2), S.0_7(4)> if (S.0_3 > 2) goto <bb 5>; [33.33%] else goto <bb 4>; [66.67%] _1 = S.0_3 + -1; _2 = &a[_1]; __builtin_memset (_2, 32, 24); S.0_7 = S.0_3 + 1; goto <bb 3>; [100.00%] but somehow we fail to see that while the first [24] is 16 byte aligned, the second is not: .L4: leaq -3(%rax,%rax,2), %rcx leaq 0(,%rcx,8), %rdx leaq -56(%rsp,%rdx), %rdx movdqa .LC0(%rip), %xmm0 movaps %xmm0, (%rdx) movabsq $2314885530818453536, %rsi movq %rsi, 16(%rdx) addq $1, %rax .L3: cmpq $2, %rax jle .L4 we shouldn't have used movaps %xmm0, (%rdx) here. Probably middle-end but bisection will show.
next prev parent reply other threads:[~2022-07-18 8:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-17 0:59 [Bug fortran/106331] New: " stuart_mentzer at objexx dot com 2022-07-17 19:26 ` [Bug fortran/106331] [12/13 Regression] " anlauf at gcc dot gnu.org 2022-07-18 7:21 ` tkoenig at gcc dot gnu.org 2022-07-18 8:10 ` rguenth at gcc dot gnu.org [this message] 2022-07-18 8:56 ` [Bug fortran/106331] [12/13 Regression] Whole array assignment of empty string segfaults with -Og since r12-2633-ge5e164effa30fd2b marxin at gcc dot gnu.org 2022-07-18 14:34 ` hjl.tools at gmail dot com 2022-07-18 14:43 ` hjl.tools at gmail dot com 2022-07-19 3:37 ` hjl.tools at gmail dot com 2022-07-19 7:41 ` rguenth at gcc dot gnu.org 2022-07-19 9:17 ` cvs-commit at gcc dot gnu.org 2022-07-19 9:18 ` [Bug middle-end/106331] [10/11/12 " rguenth at gcc dot gnu.org 2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org 2022-07-19 11:43 ` [Bug middle-end/106331] [10/11 " rguenth at gcc dot gnu.org 2022-10-11 13:04 ` cvs-commit at gcc dot gnu.org 2022-10-14 10:47 ` [Bug middle-end/106331] [10 " cvs-commit at gcc dot gnu.org 2022-10-14 10:48 ` rguenth 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-106331-4-Po185TdtFh@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: linkBe 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).