From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@oss.sgi.com
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: New binutils for kernel
Date: Tue, 20 Aug 2002 16:29:59 +0200 [thread overview]
Message-ID: <20020820162959.A26852@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1020820161204.8700H-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Aug 20, 2002 at 04:19:35PM +0200
On Tue, Aug 20, 2002 at 04:19:35PM +0200, Maciej W. Rozycki wrote:
> On Mon, 19 Aug 2002, Ralf Baechle wrote:
>
> > > Are you sure? I believe the patch effectively forces everyone to use
> > > binutils 2.13 for mips64. Is it really acceptable now?
> >
> > In the past week I ended up more and more kludging around binutils bugs.
> > We need something newer and distributions seem to be all at ~ 2.12 at least.
>
> While 2.12 may be OK from the file format point of view, there are
> serious bugs leading to bad code. So bad the kernel doesn't work. It's
> really 2.13 that is needed. I have another less important fix that will
> hopefully go in to 2.13.1 and all gcc versions are broken without yet
> another fix (it bites in mm/mmap.c; not sure if fatally).
>
> > So I guess it's time to bite the bullet?
>
> Since I'm using 2.13 anyway, it's alike to me. But it should be
> discussed at the list, IMO.
Yep. It won't hurt most of us kernel hackers very much but in particular
the distribution people may want to comment.
So any comments?
Ralf
next parent reply other threads:[~2002-08-20 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020819171238.A7457@linux-mips.org>
[not found] ` <Pine.GSO.3.96.1020820161204.8700H-100000@delta.ds2.pg.gda.pl>
2002-08-20 14:29 ` Ralf Baechle [this message]
2002-08-20 14:50 ` New binutils for kernel Daniel Jacobowitz
2002-08-20 14:58 ` Ralf Baechle
2002-08-20 15:02 ` Daniel Jacobowitz
2002-08-20 15:08 ` Maciej W. Rozycki
2002-08-20 15:11 ` Daniel Jacobowitz
2002-08-20 15:17 ` Ralf Baechle
2002-08-20 15:10 ` H. J. Lu
2002-08-20 17:27 ` Karsten Merker
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=20020820162959.A26852@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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