public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tpg+gcc at mutabah dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105860] Miscompilation causing clobbered union contents
Date: Wed, 15 Jun 2022 12:05:41 +0000	[thread overview]
Message-ID: <bug-105860-4-PFN8EhhXEe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105860-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from John Hodge <tpg+gcc at mutabah dot net> ---
Created attachment 53144
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53144&action=edit
Reproduction, partially minimised and including assertion

Attached is an updated reproduction, that includes asserts.
This fails the assert when compiled with gcc 10.3.0-1ubuntu1~20.04 when -O1 is
passed, and passes when no optimisation is enabled.

(Platform is x86_64, in case that wasn't already obvious from the disassembly)

  parent reply	other threads:[~2022-06-15 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 12:51 [Bug analyzer/105860] New: " tpg+gcc at mutabah dot net
2022-06-15 11:43 ` [Bug middle-end/105860] " marxin at gcc dot gnu.org
2022-06-15 12:05 ` tpg+gcc at mutabah dot net [this message]
2022-06-15 12:50 ` [Bug middle-end/105860] [10/11/12/13 Regression] Miscompilation causing clobbered union contents since r10-918-gc56c86024f8fba0c marxin at gcc dot gnu.org
2022-06-15 23:20 ` pinskia at gcc dot gnu.org
2022-06-28 10:49 ` jakub at gcc dot gnu.org
2022-07-01 18:12 ` jamborm at gcc dot gnu.org
2022-07-01 20:49 ` [Bug tree-optimization/105860] " jamborm at gcc dot gnu.org
2022-07-04 15:08 ` cvs-commit at gcc dot gnu.org
2022-07-11 16:47 ` cvs-commit at gcc dot gnu.org
2022-07-12 11:18 ` cvs-commit at gcc dot gnu.org
2022-07-13 11:19 ` cvs-commit at gcc dot gnu.org
2022-07-13 11:19 ` jamborm 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-105860-4-PFN8EhhXEe@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).