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 tree-optimization/94130] [8/9/10 Regression] Unintended result with optimization option when assigning two structures, memset and 0
Date: Wed, 11 Mar 2020 07:58:16 +0000	[thread overview]
Message-ID: <bug-94130-4-8BYwc6z3tQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94130-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94130

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Doing

    memset(&s_myvalue, 0, sizeof(s_myvalue));
    s_myreq.m_data = &s_myvalue;

also works around the issue.  Odd.

  parent reply	other threads:[~2020-03-11  7:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  1:47 [Bug c/94130] New: " minzkn at minzkn dot com
2020-03-11  7:55 ` [Bug tree-optimization/94130] [8/9/10 Regression] " rguenth at gcc dot gnu.org
2020-03-11  7:58 ` rguenth at gcc dot gnu.org [this message]
2020-03-11 12:05 ` jakub at gcc dot gnu.org
2020-03-11 12:15 ` jakub at gcc dot gnu.org
2020-03-11 12:17 ` jakub at gcc dot gnu.org
2020-03-11 12:21 ` jakub at gcc dot gnu.org
2020-03-11 13:06 ` jakub at gcc dot gnu.org
2020-03-12 10:14 ` [Bug tree-optimization/94130] [8/9 " jakub at gcc dot gnu.org
2020-03-12 12:38 ` marxin at gcc dot gnu.org
2020-03-17 18:57 ` cvs-commit at gcc dot gnu.org
2020-03-17 19:14 ` [Bug tree-optimization/94130] [8 " jakub at gcc dot gnu.org
2020-09-17 14:24 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:18 ` jakub at gcc dot gnu.org
2021-03-06 18:10 ` jakub 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-94130-4-8BYwc6z3tQ@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).