public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: binutils@sourceware.cygnus.com
Subject: Large changes checked in
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990603073507.17700.qmail@daffy.airs.com> (raw)

I checked in some large changes to the hash table, the scrubber, and
the symbol handling code.

The symbol handling changes are the worst.  These will probably break
most targets.  I checked and fixed many popular ones.  I'll fix the
rest over time.  If you run into trouble, let me know.  Failure is
indicated by a failure to compile.

The goal was to speed up gas on large files.  On a particular 27M
input file I was using as a test case, these patches change gas from
130.44+2.52 user+cpu time and 46M of memory to 44.85+1.65 and 34M.
Wall time on my system with 64M of real memory went from 2:42 to 0:53.

Please let me know about any problems.

Ian

             reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Ian Lance Taylor [this message]
1999-07-01  0:00 ` Snapshot? Jerry Quinn
1999-07-01  0:00   ` Snapshot? Ian Lance Taylor
1999-07-01  0:00     ` Snapshot? Jerry Quinn

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=19990603073507.17700.qmail@daffy.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sourceware.cygnus.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).