From: Diego Novillo <dnovillo@google.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][RFC] Make called function type explicit, make function pointer type conversions useless
Date: Mon, 11 Apr 2011 13:18:00 -0000 [thread overview]
Message-ID: <BANLkTikKWyZox8QpdSySyW3Bc4EvgQq+cA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1104081744100.810@zhemvz.fhfr.qr>
On Fri, Apr 8, 2011 at 11:49, Richard Guenther <rguenther@suse.de> wrote:
> I'll leave this for comments over the weekend, and if there are none
> will go ahead and check this in early next week.
The approach looks fine to me. Thanks.
Diego.
next prev parent reply other threads:[~2011-04-11 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 15:49 Richard Guenther
2011-04-11 13:18 ` Diego Novillo [this message]
2011-04-12 10:44 ` Richard Guenther
2011-04-13 2:28 ` H.J. Lu
2011-04-14 9:57 ` Eric Botcazou
2011-04-14 10:15 ` Richard Guenther
2011-04-14 13:40 ` Richard Guenther
2011-04-14 15:58 ` Eric Botcazou
2011-04-14 16:05 ` Richard Guenther
2011-04-14 16:37 ` Eric Botcazou
2011-04-15 9:29 ` Richard Guenther
2011-04-15 3:00 ` Eric Botcazou
2011-04-15 8:20 ` Eric Botcazou
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=BANLkTikKWyZox8QpdSySyW3Bc4EvgQq+cA@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).