public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <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 since r12-2633-ge5e164effa30fd2b
Date: Mon, 18 Jul 2022 14:43:40 +0000	[thread overview]
Message-ID: <bug-106331-4-nTr1g1aRi4@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

--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
This is a latent bug. GCC 11 RTL expander generates:

(insn 21 20 22 (set (mem/c:TI (reg:DI 92 [ D.3947 ]) [0 MEM <c_char[0:]> [(void 
*)&a]+0 S16 A128])
        (const_wide_int 0x20202020202020202020202020202020)) "x.f90":3:6 -1
     (nil))

[(void *)&a]+0 S16 A128] doesn't look right.

  parent reply	other threads:[~2022-07-18 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  0:59 [Bug fortran/106331] New: Whole array assignment of empty string segfaults with -Og 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
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 [this message]
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-nTr1g1aRi4@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).