public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/47059] compiler fails to coalesce loads/stores Date: Fri, 22 Jan 2021 17:11:03 +0000 [thread overview] Message-ID: <bug-47059-4-Wp5eeGxlTc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47059 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:d7e681fc3afff24a6279058cbb0b0dc4cd96be8c commit r11-6862-gd7e681fc3afff24a6279058cbb0b0dc4cd96be8c Author: Martin Jambor <mjambor@suse.cz> Date: Fri Jan 22 18:09:38 2021 +0100 Testcase for old PR 47059 I stumbled across PR 47059 from 2010 which has been addressed by store-merging. I am going to close it but would like to add its testcase too. gcc/testsuite/ChangeLog: 2021-01-08 Martin Jambor <mjambor@suse.cz> PR tree-optimization/47059 * gcc.dg/tree-ssa/pr47059.c: New test.
prev parent reply other threads:[~2021-01-22 17:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-24 11:01 [Bug tree-optimization/47059] New: " rahul at icerasemi dot com 2011-01-15 13:36 ` [Bug tree-optimization/47059] " rahul at icerasemi dot com 2011-01-15 14:41 ` rahul at icerasemi dot com 2013-09-18 10:06 ` vda.linux at googlemail dot com 2021-01-08 17:58 ` jamborm at gcc dot gnu.org 2021-01-08 17:58 ` jamborm at gcc dot gnu.org 2021-01-22 17:11 ` cvs-commit at gcc dot gnu.org [this message]
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-47059-4-Wp5eeGxlTc@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).