From: "Diego Novillo" <dnovillo@google.com>
To: "Kenneth Zadeck" <zadeck@naturalbridge.com>
Cc: "Jim Blandy" <jimb@codesourcery.com>,
"Mark Mitchell" <mark@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"William Maddox" <maddox@google.com>
Subject: Re: [lto] patch committed to fix calls and FUNCTION_DECLS
Date: Tue, 28 Aug 2007 17:05:00 -0000 [thread overview]
Message-ID: <b798aad50708280957n15fdc0dakae33fbb840b52650@mail.gmail.com> (raw)
In-Reply-To: <46D4525E.9060209@naturalbridge.com>
On 8/28/07, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
> 2007-08-28 Kenneth Zadeck <zadeck@naturalbridge.com>
>
> * lto-function-out (output_expr_operand): Reorder the fields
> in the stream for CALL_EXPRs.
> (lto_static_init): Do not put out types for FUNCTION_DECLs.
The patch is missing. Also, could you describe what those problems
were? It tends to be useful when doing archeology in the future.
Thanks.
next prev parent reply other threads:[~2007-08-28 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 17:02 Kenneth Zadeck
2007-08-28 17:05 ` Diego Novillo [this message]
2007-08-28 17:45 ` Kenneth Zadeck
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=b798aad50708280957n15fdc0dakae33fbb840b52650@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimb@codesourcery.com \
--cc=maddox@google.com \
--cc=mark@codesourcery.com \
--cc=zadeck@naturalbridge.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).