public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30913] SRA bugs with anon bitfields
Date: Thu, 22 Feb 2007 23:46:00 -0000 [thread overview]
Message-ID: <20070222234558.23310.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30913-87@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2007-02-22 23:45 -------
The second part of this bug is recorded as PR 22156.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30913
next prev parent reply other threads:[~2007-02-22 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 14:28 [Bug tree-optimization/30913] New: " jakub at gcc dot gnu dot org
2007-02-21 15:18 ` [Bug tree-optimization/30913] " pinskia at gcc dot gnu dot org
2007-02-22 23:46 ` pinskia at gcc dot gnu dot org [this message]
2010-04-09 10:58 ` jiez at gcc dot gnu dot org
2010-04-09 11:03 ` rguenth at gcc dot gnu dot 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=20070222234558.23310.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).