public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36602] memset should be optimized into an empty CONSTRUCTOR
Date: Sun, 22 Jun 2008 21:26:00 -0000 [thread overview]
Message-ID: <20080622212609.20054.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36602-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from rguenth at gcc dot gnu dot org 2008-06-22 21:26 -------
Confirmed.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2008-06-22 21:26:09
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36602
next prev parent reply other threads:[~2008-06-22 21:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 21:06 [Bug tree-optimization/36602] New: " pinskia at gcc dot gnu dot org
2008-06-22 21:26 ` rguenth at gcc dot gnu dot org [this message]
2010-03-02 18:52 ` [Bug tree-optimization/36602] " pinskia at gcc dot gnu dot org
[not found] <bug-36602-4@http.gcc.gnu.org/bugzilla/>
2011-06-22 20:31 ` ak at gcc dot gnu.org
2012-06-06 10:20 ` rguenth at gcc dot gnu.org
2012-06-06 14:11 ` rguenth at gcc dot gnu.org
2012-06-06 14:13 ` rguenth at gcc dot gnu.org
2012-06-06 16:36 ` jason at gcc dot gnu.org
2012-06-11 10:58 ` rguenth at gcc dot gnu.org
2014-09-28 17:19 ` andi-gcc at firstfloor dot org
2014-09-29 10:34 ` rguenth at gcc dot gnu.org
2021-01-08 16:37 ` jamborm at gcc dot gnu.org
2021-01-11 7:12 ` rguenth at gcc dot gnu.org
2024-06-26 17:29 ` crrodriguez at opensuse dot org
2024-06-27 6:09 ` 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=20080622212609.20054.qmail@sourceware.org \
--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).