From: Jakub Jelinek <jakub@redhat.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Optimize C++ comdat ctors/dtors in classes without virtual bases (PR c++/3187, take 5)
Date: Fri, 04 Dec 2009 18:29:00 -0000 [thread overview]
Message-ID: <20091204182132.GJ22813@hs20-bc2-1.build.redhat.com> (raw)
In-Reply-To: <4B195605.60804@gmail.com>
On Fri, Dec 04, 2009 at 06:33:41PM +0000, Dave Korn wrote:
> I assumed it was, but for reasons stated elsewhere it wasn't practical to
> run with full checking on so I tested it unchecked; nothing untoward happened.
I think cygwin doesn't HAVE_COMDAT_GROUP anyway, so it wouldn't make any
difference.
Jakub
next prev parent reply other threads:[~2009-12-04 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 22:38 [C++ PATCH] Optimize C++ comdat ctors/dtors in classes without virtual bases (PR c++/3187, take 3) Jakub Jelinek
2009-12-01 3:53 ` Jason Merrill
2009-12-01 8:07 ` Jakub Jelinek
2009-12-01 15:39 ` Jason Merrill
2009-12-01 9:52 ` [C++ PATCH] Optimize C++ comdat ctors/dtors in classes without virtual bases (PR c++/3187, take 4) Jakub Jelinek
2009-12-01 15:40 ` Jakub Jelinek
2009-12-01 16:38 ` Dave Korn
2009-12-01 19:35 ` [C++ PATCH] Optimize C++ comdat ctors/dtors in classes without virtual bases (PR c++/3187, take 5) Jakub Jelinek
2009-12-01 20:14 ` Jason Merrill
2009-12-01 21:03 ` Dave Korn
2009-12-04 18:19 ` Dave Korn
2009-12-04 18:29 ` Jakub Jelinek [this message]
2009-12-04 18:46 ` Dave Korn
2009-12-27 13:36 ` H.J. Lu
2009-12-01 21:15 ` [C++ PATCH] Optimize C++ comdat ctors/dtors in classes without virtual bases (PR c++/3187, take 3) Daniel Jacobowitz
2009-12-01 21:20 ` Jakub Jelinek
2009-12-01 21:50 ` Daniel Jacobowitz
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=20091204182132.GJ22813@hs20-bc2-1.build.redhat.com \
--to=jakub@redhat.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).