From: Diego Novillo <dnovillo@google.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] use build_function_type less in c-family and LTO
Date: Tue, 10 May 2011 15:17:00 -0000 [thread overview]
Message-ID: <BANLkTimpBq6Q4RyLnL=sHzOfJ4cqkjwE6g@mail.gmail.com> (raw)
In-Reply-To: <20110510131438.GT23480@codesourcery.com>
On Tue, May 10, 2011 at 10:14, Nathan Froyd <froydnj@codesourcery.com> wrote:
> gcc/c-family/
> * c-common.c (def_fn_type): Don't call build_function_type, call
> build_function_type_vec or build_varargs_function_type_vec instead.
> (c_common_nodes_and_builtins): Likewise.
>
> gcc/lto/
> * lto-lang.c (def_fn_type): Don't call build_function_type, call
> build_function_type_vec or build_varargs_function_type_vec instead.
OK for LTO.
Diego.
next prev parent reply other threads:[~2011-05-10 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 14:05 Nathan Froyd
2011-05-10 15:17 ` Diego Novillo [this message]
2011-05-10 15:25 ` Joseph S. Myers
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='BANLkTimpBq6Q4RyLnL=sHzOfJ4cqkjwE6g@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@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).