public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106131] [10/11/12/13 Regression] -fstrict-aliasing breaks normal program that does not use any pointer or reference
Date: Thu, 30 Jun 2022 06:47:59 +0000	[thread overview]
Message-ID: <bug-106131-4-zzQid3dJYI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106131-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 29 Jun 2022, mpolacek at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
> 
> --- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
> Started with
> 
> commit 8403c2cf5f66758fc78a01a675b0d218fded0202
> Author: Richard Biener <rguenther@suse.de>
> Date:   Mon Nov 24 14:07:18 2014 +0000

I think that just exposed it.  Btw, I've not got to the point 
understanding what actual transform makes the testcase fail (nor
spot the relevant difference in .optimized).

  parent reply	other threads:[~2022-06-30  6:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  2:05 [Bug c++/106131] New: " 18307130172 at fudan dot edu.cn
2022-06-29  2:09 ` [Bug c++/106131] " 18307130172 at fudan dot edu.cn
2022-06-29  2:36 ` pinskia at gcc dot gnu.org
2022-06-29  9:26 ` redi at gcc dot gnu.org
2022-06-29 19:20 ` [Bug c++/106131] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-06-29 19:21 ` pinskia at gcc dot gnu.org
2022-06-29 19:38 ` mpolacek at gcc dot gnu.org
2022-06-29 19:39 ` [Bug tree-optimization/106131] " mpolacek at gcc dot gnu.org
2022-06-29 19:39 ` mpolacek at gcc dot gnu.org
2022-06-30  0:50 ` 18307130172 at fudan dot edu.cn
2022-06-30  6:47 ` rguenther at suse dot de [this message]
2022-06-30  7:57 ` rguenth at gcc dot gnu.org
2022-06-30  8:31 ` rguenth at gcc dot gnu.org
2022-07-01  6:53 ` cvs-commit at gcc dot gnu.org
2022-07-01  6:54 ` [Bug tree-optimization/106131] [10/11/12 " rguenth at gcc dot gnu.org
2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org
2022-10-11 13:04 ` [Bug tree-optimization/106131] [10/11 " cvs-commit at gcc dot gnu.org
2022-10-14 10:47 ` [Bug tree-optimization/106131] [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-106131-4-zzQid3dJYI@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).