From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Caroline Tice <cmtice@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
libstdc++@gcc.gnu.org, Diego Novillo <dnovillo@google.com>,
Luis Lozano <llozano@google.com>,
Bhaskar Janakiraman <bjanakiraman@google.com>
Subject: Re: [PATCH, updated] Vtable pointer verification, runtime library changes (patch 3 of 3)
Date: Fri, 08 Mar 2013 00:12:00 -0000 [thread overview]
Message-ID: <CAH6eHdRvVP9hY3BLbzQmpFCB6UhQ-NfC_WfnAdySDr+Q6MgrLQ@mail.gmail.com> (raw)
In-Reply-To: <CABtf2+RG_5UCccD8obJA3FRbMdumS3u5FQPF6dkyDZtO1J9ZaA@mail.gmail.com>
On 7 March 2013 23:53, Caroline Tice wrote:
> Hello,
>
> I believe this patch addresses all of your comments; I modified the
> configure.ac files to generate the configures, and I fixed the
> spelling mistakes in the comments. I still get the warnings when
> generating the Makefile.in files from the Makefile.am files, but the
> resulting files seem to be correct, and I don't know how to make the
> warnings go away.
>
> Please review this patch and let me know if it will be ok to commit
> when GCC opens up again.
I'd like to know if someone with better automake skills than I have
can do anything about that warning, but otherwise that looks OK to me,
thanks.
next prev parent reply other threads:[~2013-03-08 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 19:31 Caroline Tice
2013-02-25 19:53 ` Caroline Tice
2013-02-25 21:15 ` Jonathan Wakely
2013-02-25 22:44 ` Caroline Tice
2013-02-25 22:49 ` Jonathan Wakely
2013-03-07 23:53 ` Caroline Tice
2013-03-08 0:12 ` Jonathan Wakely [this message]
2013-03-08 8:13 ` Dave Korn
2013-05-21 2:01 ` Benjamin De Kosnik
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=CAH6eHdRvVP9hY3BLbzQmpFCB6UhQ-NfC_WfnAdySDr+Q6MgrLQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=bjanakiraman@google.com \
--cc=cmtice@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=llozano@google.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).