public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mdorey at bluearc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17519] [4.0/4.1/4.2 Regression] Warning for array of packed non-POD in packed struct
Date: Sun, 25 Nov 2007 21:41:00 -0000 [thread overview]
Message-ID: <20071125214109.17709.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17519-3259@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from mdorey at bluearc dot com 2007-11-25 21:41 -------
(We finally got round to throwing the switch on our next release from gcc-3.3
to gcc-4.2. It works great - the compiled code gets us significantly higher
benchmark numbers and we're appreciating improved error reporting from the
compiler. This PR had been the killer obstacle, so many, if belated, thanks to
Jason for sorting this out.)
--
mdorey at bluearc dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mdorey at bluearc dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17519
prev parent reply other threads:[~2007-11-25 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17519-3259@http.gcc.gnu.org/bugzilla/>
2005-10-23 19:54 ` [Bug c++/17519] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-30 22:55 ` mmitchel at gcc dot gnu dot org
2006-02-10 18:22 ` [Bug c++/17519] [3.4/4.0/4.1/4.2 " amylaar at gcc dot gnu dot org
2006-02-15 11:53 ` titusjan at gmail dot com
2006-02-16 20:12 ` nathan at gcc dot gnu dot org
2006-02-17 8:39 ` titusjan at gmail dot com
2006-02-24 0:25 ` mmitchel at gcc dot gnu dot org
2006-05-25 2:35 ` [Bug c++/17519] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-07-06 2:09 ` jason at gcc dot gnu dot org
2006-07-06 2:21 ` jason at gcc dot gnu dot org
2006-07-06 3:33 ` jason at gcc dot gnu dot org
2006-07-06 3:45 ` jason at gcc dot gnu dot org
2007-11-25 21:41 ` mdorey at bluearc dot com [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=20071125214109.17709.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).