public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29442] insn-attrtab has grown too large
Date: Mon, 07 May 2012 12:29:00 -0000	[thread overview]
Message-ID: <bug-29442-4-1NXWVnG1m9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29442-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29442

--- Comment #18 from Michael Matz <matz at gcc dot gnu.org> 2012-05-07 12:27:18 UTC ---
(In reply to comment #15)
> While looking for ways to speed up genattrtab itself, I found this patch, which
> doesn't speed up genattrtab, but would make the insn-*tab.c files smaller:
> 
> http://gcc.gnu.org/ml/gcc-patches/2003-09/msg00316.html
> 
> Micha, this appears to have been dropped. Any reason why you never asked for an
> OK to commit this patch?

I did on multiple occasions (last was
http://gcc.gnu.org/ml/gcc-patches/2010-06/msg01521.html) , never got an okay. 

Meanwhile Jakub implemented a different mean which doesn't call the get_attr_
functions dynamically more often (which my approach potentially does), but
which as result isn't nearly as effective in reducing size and compile and
generation time.

Some of the hunks of my patch still are useful cleanups/speedups, lemme
submit them.


  parent reply	other threads:[~2012-05-07 12:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29442-4@http.gcc.gnu.org/bugzilla/>
2012-05-02 16:29 ` gasper.azman at gmail dot com
2012-05-02 16:53 ` manu at gcc dot gnu.org
2012-05-04 20:05 ` steven at gcc dot gnu.org
2012-05-04 20:19 ` steven at gcc dot gnu.org
2012-05-07  0:19 ` steven at gcc dot gnu.org
2012-05-07  7:55 ` jakub at gcc dot gnu.org
2012-05-07  8:35 ` jakub at gcc dot gnu.org
2012-05-07 12:29 ` matz at gcc dot gnu.org [this message]
2012-05-07 12:38 ` jakub at gcc dot gnu.org
2006-10-12 16:11 [Bug other/29442] New: " rick at hartmantech dot com
2006-10-14  3:39 ` [Bug other/29442] " pinskia at gcc dot gnu dot org
2006-10-14  4:16 ` vapier at gentoo dot org
2006-10-25 12:44 ` JoeGTN1 at NetZero dot net
2006-10-25 16:23 ` rick at hartmantech dot com
2007-07-23  5:53 ` konig12 at gmail dot com
2007-10-27 12:47 ` rask at gcc dot gnu dot org
2007-10-28 12:40 ` rask at gcc dot gnu dot org
2007-10-28 12:57 ` rask at gcc dot gnu dot org
2007-10-28 17:48 ` rask at gcc dot gnu dot org
2009-02-22 14:19 ` steven at gcc dot gnu dot org

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=bug-29442-4-1NXWVnG1m9@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).