From: Cary Coutant <ccoutant@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] comdat types
Date: Tue, 21 Jul 2009 00:10:00 -0000 [thread overview]
Message-ID: <c17be2b30907201436t1c852211u11887533091c5ad1@mail.gmail.com> (raw)
In-Reply-To: <m3prc1hj0h.fsf@fleche.redhat.com>
> BTW, what is the status of the GCC patch?
I have one bug that I need to fix on the dwarf4 branch in gcc, then I
need to do another merge from trunk and fix any breakage that causes.
After that, the branch should be ready to merge into the trunk. I hope
to have that bug fixed this week.
-cary
next prev parent reply other threads:[~2009-07-20 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 0:04 Doug Evans
2009-06-25 19:47 ` Tom Tromey
2009-06-25 20:28 ` Doug Evans
2009-06-25 20:49 ` Tom Tromey
2009-07-15 1:13 ` Doug Evans
2009-07-15 19:28 ` Tom Tromey
2009-07-16 1:25 ` Doug Evans
2009-07-21 0:10 ` Cary Coutant [this message]
2009-06-26 1:33 ` Daniel Jacobowitz
2009-06-26 0:01 ` Cary Coutant
2009-06-26 0:54 ` Doug Evans
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=c17be2b30907201436t1c852211u11887533091c5ad1@mail.gmail.com \
--to=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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