From: ralf@uni-koblenz.de
To: Honza Pazdziora <adelton@informatics.muni.cz>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Lmbench for RH 5.1
Date: Thu, 9 Jul 1998 15:39:20 +0200 [thread overview]
Message-ID: <19980709153920.50904@uni-koblenz.de> (raw)
In-Reply-To: <199807091317.PAA02524@aisa.fi.muni.cz>; from Honza Pazdziora on Thu, Jul 09, 1998 at 03:17:22PM +0200
On Thu, Jul 09, 1998 at 03:17:22PM +0200, Honza Pazdziora wrote:
> I wanted to do benchmarks on my Indy. The versions 1.0 and 1.1 fail
> when compiling lat_ctx.c with assembler messages:
> Error: Branch out of range on lines 4189 and 40323. When I try to
This is a GAS problem, I doesn't know how to express branches beyond the
16 bit range of a branch instruction as machine instructions. Newer
lmbench versions don't run into that GAS problem anymore.
> compile it with -O2, it starts optimizing but doesn't seem to finish.
Don't optimize lmbench, the compiler might decide to just throw parts
of lmbench away producing awsome results. lat_ctx optimized with -O2
hits GCC on one of it's weak points, it will finish to optimize but
will need very long.
> The version 2beta6 of lmbench complains about missing
> linux/autoconf.h.
You probably ran make distclean on the kernel source tree? Don't, best
leave the kernel source tree configured around, so just use make clean.
The question what is trying to use autoconf.h for what reason remains;
user code isn't supposed to use this file.
(Alex: the kernel source rpm should be installed configured, especially
including autoconf.h for compatibility.)
> This is RH 5.1 Alpha 1 installer with Alpha 2 RPM's placed over the
> Alpha 1 ones, with gcc from redhat-5.0 (Alex, we should put gcc
> to the distribution). Do you have any idea what to do with any
> of these problems? Or do you have precompiled lmbench somewhere?
No, because lmbench normally builds just out of the box.
(The networking code for the kernel which is going to ship with RH
has a couple of crude fixed due to lack of time, don't benchmark to
hard ...)
Ralf
next prev parent reply other threads:[~1998-07-09 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-14 4:44 RedHat 5.1 (Manhattan) ALPHA 1 for SGI/Indys Alex deVries
1998-06-16 15:46 ` Honza Pazdziora
1998-06-16 15:46 ` Honza Pazdziora
1998-06-16 16:07 ` Alex deVries
1998-06-16 18:25 ` Honza Pazdziora
1998-06-16 18:25 ` Honza Pazdziora
1998-06-24 13:04 ` Daniel Veillard
1998-06-24 19:22 ` Alex deVries
1998-07-09 13:17 ` Lmbench for RH 5.1 Honza Pazdziora
1998-07-09 13:39 ` ralf [this message]
1998-07-09 13:47 ` Honza Pazdziora
1998-07-09 13:53 ` ralf
1998-07-09 16:06 ` Ulf Carlsson
1998-06-16 20:25 ` RedHat 5.1 (Manhattan) ALPHA 1 for SGI/Indys Tomi Leppikangas
1998-06-18 0:28 ` Alex deVries
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=19980709153920.50904@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adelton@informatics.muni.cz \
--cc=linux@cthulhu.engr.sgi.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