public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <davem@davemloft.net>
Cc: <binutils@sources.redhat.com>
Subject: Re: Use of as_fatal
Date: Tue, 19 Apr 2005 06:40:00 -0000	[thread overview]
Message-ID: <s264b601.099@emea1-mh.id2.novell.com> (raw)

>I fixed the as_fatal() which was tripping up the macro dot testcases.
>Patch below.

Thanks.

>While macro dot appears to be fixes on Sparc, the new macro purge testcase
>seems to hang infinitely.  As far as I can tell it is trying to expand macros
>over and over for some reason.  I thought initially this was caused
>by tc-sparc.c:sparc_ip()'s modification of the string it is given,
>yet tests of making sparc_ip() not do this didn't fix the problem.

Hmm, that sounds odd. The test expands and purges 26**4 macros, to check that the purging reclaims the memory used for the macro definition; there's certainly some memory implicitly used elsewhere that can't be reclaimed, so it still shows an increasing memory usage over the time it runs. On the EM64T system I used to test this, it takes far less than a minute to complete (without the late addition of --hash-size it took several minutes), so I'd expect other systems, unless equipped with very little memory, to be able to cope with this test, too (without the purging, the loss of memory was in the range of gigabytes, so especially on 32-bit boxes it would complete only after a very long time of heavy swapping, if at all). So I guess the question regarding your observation is whether it indeed hangs (which I can't imagine) or just makes very slow progress (and if so, for what reason).

Jan

             reply	other threads:[~2005-04-19  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  6:40 Jan Beulich [this message]
2005-04-19 19:06 ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2005-04-18 13:12 Jan Beulich
2005-04-18 20:25 ` David S. Miller

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=s264b601.099@emea1-mh.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=binutils@sources.redhat.com \
    --cc=davem@davemloft.net \
    /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).