From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Kip Walker <kwalker@broadcom.com>,
linux-mips@oss.sgi.com
Subject: Re: .section problems in entry.S
Date: Thu, 13 Dec 2001 16:28:16 -0500 [thread overview]
Message-ID: <20011213162816.B6983@nevyn.them.org> (raw)
In-Reply-To: <20011213184541.A7171@dea.linux-mips.net>
On Thu, Dec 13, 2001 at 06:45:42PM -0200, Ralf Baechle wrote:
> On Mon, Dec 10, 2001 at 05:03:41PM +0100, Maciej W. Rozycki wrote:
>
> > > Certainly not. The problem is known and so far I've just hacked around
> > > it more or less elegant. But it's a trap and so I think we've got good
> > > reasons to force people to upgrade to a newer assembler than the current
> > > minimal version. The question is which - I don't like frequent tool
> > > upgrades.
> >
> > There are no working released binutils for a modern MIPS/Linux system,
> > AFAIK. However, version 2.11.92 from the CVS seems to work reasonably
> > well now, so chances are the next release will do as well. Maybe 2.12
> > will be a good candidate then, once it is released and tested a bit.
>
> What is the schedule for 2.12?
There isn't one yet; I'm hoping within three months. I'm going to try
to roll the ball a little this week.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-13 22:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 18:05 .section problems in entry.S Kip Walker
2001-12-10 0:18 ` Ralf Baechle
2001-12-10 16:03 ` Maciej W. Rozycki
2001-12-13 20:45 ` Ralf Baechle
2001-12-13 21:12 ` Thiemo Seufer
2001-12-13 21:27 ` Daniel Jacobowitz
2001-12-13 22:13 ` Thiemo Seufer
2001-12-13 22:21 ` Daniel Jacobowitz
2001-12-13 21:28 ` Daniel Jacobowitz [this message]
2001-12-13 21:37 ` Ralf Baechle
2001-12-13 21:41 ` Daniel Jacobowitz
2001-12-14 14:47 ` Maciej W. Rozycki
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=20011213162816.B6983@nevyn.them.org \
--to=dan@debian.org \
--cc=kwalker@broadcom.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.