public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Jan Hubicka <hubicka@ucw.cz>,
	Nathan Froyd <froydnj@codesourcery.com>,
	Richard Guenther <richard.guenther@gmail.com>,
	Mark Mitchell <mark@codesourcery.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: Speed up genattrtab
Date: Thu, 17 Jun 2010 11:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1006171338060.11284@wotan.suse.de> (raw)
In-Reply-To: <4C1903D1.1070401@gnu.org>

Hi,

On Wed, 16 Jun 2010, Paolo Bonzini wrote:

> On 06/16/2010 05:51 PM, Jan Hubicka wrote:
> > With a lot of cores, we might actually execute getnattrtab and compilation
> > of stage1 insn-attrtab.c at same time and then just sanity check that
> > genattrtab
> > did not change results :)
> 
> That's a different story.  It doesn't break the idea of bootstrapping, 
> and can be applied to all insn-* files.

But it also doesn't give any gains.  You still would have to run 
genattrtab (to get something to compare with), and you still would have to 
compile insn-attrtab.c (to check that cc1 produced the same code as last 
stage).


Ciao,
Michael.

  reply	other threads:[~2010-06-17 11:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 16:58 Michael Matz
2010-06-15 17:37 ` Mark Mitchell
2010-06-15 17:37   ` Jan Hubicka
2010-06-15 19:13     ` Mark Mitchell
2010-06-15 19:17       ` Ralf Wildenhues
2010-06-15 19:22       ` Jakub Jelinek
2010-06-16 15:42         ` Jakub Jelinek
2010-06-16 15:59           ` Jan Hubicka
2010-06-16 20:27           ` Jakub Jelinek
2010-06-16 21:50             ` Mark Mitchell
2010-06-17 10:21               ` Jakub Jelinek
2010-06-17 11:50                 ` Jan Hubicka
2010-06-17 13:39                 ` Michael Matz
2010-06-17 15:24                   ` Mark Mitchell
2010-06-17 18:09                     ` Michael Matz
2010-06-17 18:44                       ` Mark Mitchell
2010-06-17 12:27             ` Jakub Jelinek
2010-06-16  9:32       ` Richard Guenther
2010-06-16 14:30         ` Nathan Froyd
2010-06-16 14:33           ` Michael Matz
2010-06-16 14:43             ` Nathan Froyd
2010-06-16 15:33               ` Mike Stump
2010-06-16 15:48               ` Michael Matz
2010-06-16 15:57                 ` Jan Hubicka
2010-06-16 17:21                   ` Paolo Bonzini
2010-06-17 11:56                     ` Michael Matz [this message]
2010-06-17 12:08                       ` Jan Hubicka
2010-06-17 12:20                         ` Michael Matz
2010-06-17 12:26                           ` Jan Hubicka
2010-06-17 12:14                       ` Paolo Bonzini
2010-06-15 17:59   ` Dave Korn
2010-06-15 20:30     ` Paolo Bonzini
2010-06-15 20:34       ` Paolo Bonzini
2010-06-15 22:03     ` David Daney
  -- strict thread matches above, loose matches on Subject: below --
2004-07-13 20:28 Segher Boessenkool
2004-07-13 20:35 ` Segher Boessenkool
2004-07-15  2:26   ` Vladimir Makarov
2004-07-15 18:04     ` Ranjit Mathew
2004-07-16 13:19       ` Zack Weinberg
2004-07-16 14:38     ` Segher Boessenkool

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=Pine.LNX.4.64.1006171338060.11284@wotan.suse.de \
    --to=matz@suse.de \
    --cc=bonzini@gnu.org \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mark@codesourcery.com \
    --cc=richard.guenther@gmail.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).