From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: ralf@mailhost.uni-koblenz.de
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: Fun with binutils ...
Date: Tue, 15 Jul 1997 15:48:12 -0400 [thread overview]
Message-ID: <199707151948.PAA08407@jenolan.rutgers.edu> (raw)
In-Reply-To: <199707151935.VAA00342@informatik.uni-koblenz.de> (message from Ralf Baechle on Tue, 15 Jul 1997 21:35:53 +0200 (MET DST))
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
Date: Tue, 15 Jul 1997 21:35:53 +0200 (MET DST)
- GAS still doesn't deal with _huge_ loops. The only program I know
of which is affected is lmbench, but that alone is reason enough
to fix it :-)
It is not a bug, just that we have the local label semantics specified
for linux-mips differently in gcc and gas. I fixed this ages ago and
it made lat_ctx.c compile just fine.
next prev parent reply other threads:[~1997-07-15 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-15 19:35 Fun with binutils Ralf Baechle
1997-07-15 19:48 ` David S. Miller [this message]
1997-07-15 22:15 ` Ralf Baechle
1997-07-15 22:15 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
1997-07-18 15:20 Angus MacCuish
1997-07-18 15:20 ` Angus MacCuish
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=199707151948.PAA08407@jenolan.rutgers.edu \
--to=davem@jenolan.rutgers.edu \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@mailhost.uni-koblenz.de \
/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