From: Mark Mitchell <mark@codesourcery.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
Matt Austern <austern@apple.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Committed] Use special-purpose hash table to speed up walk_tree
Date: Sun, 17 Oct 2004 08:30:00 -0000 [thread overview]
Message-ID: <4172086B.4080106@codesourcery.com> (raw)
In-Reply-To: <200410161217.43614.stevenb@suse.de>
Steven Bosscher wrote:
> On Saturday 16 October 2004 11:47, Jakub Jelinek wrote:
>
>>But on x86-64-redhat-linux essentially makes even bootstrap impossible
>>(well, I have killed it after it spent more than 10 minutes compiling
>>insn-recog or insn-attrtab by stage1/cc1).
>>hash1's distribution is less than perfect.
In that case, go ahed and revert the patch. I know that we normally
require a 48-hour period, but I know Matt, and I am confident that he
will not complain.
Then, Matt will work out how to fix it.
> It would have been nice if this patch had been tested better. Good
> for you, 2% on QT, but what are the effects on other code? And are
> we in stage3 now or not? I did not see this idea on Mark's list of
> things that would be allowed in.
There is an item for improving compile-time performance; this falls
under that.
> And why did Mark approve this offline, isn't it the policy that a
> patch is posted to gcc-patches and reviewed in public?
I don't think there is any such policy one way or the other. Certainly,
there is precedent for patches being approved offline. Matt sent me the
patch, and it looked good to me. I didn't see any reason to test it on
other architectures.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2004-10-17 5:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 23:22 Matt Austern
2004-10-14 23:24 ` Phil Edwards
2004-10-15 0:04 ` Matt Austern
2004-10-16 10:17 ` Jakub Jelinek
2004-10-16 10:37 ` Steven Bosscher
2004-10-17 8:30 ` Mark Mitchell [this message]
2004-10-17 10:59 ` Steven Bosscher
2004-10-17 18:45 ` Matt Austern
2004-10-18 4:19 ` Mark Mitchell
2004-10-21 21:25 ` Gerald Pfeifer
2004-10-16 10:42 ` Jakub Jelinek
2004-10-16 11:49 ` Jakub Jelinek
2004-10-16 18:29 ` Matt Austern
2004-10-16 18:35 ` Richard Henderson
2004-10-16 18:37 ` Jakub Jelinek
2004-10-16 18:51 ` Richard Henderson
2004-10-16 19:15 ` Jakub Jelinek
2004-10-17 1:11 ` Richard Henderson
2004-10-16 18:14 ` Matt Austern
2004-10-18 14:48 Richard Kenner
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=4172086B.4080106@codesourcery.com \
--to=mark@codesourcery.com \
--cc=austern@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=stevenb@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).