public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: cgd@broadcom.com
Cc: mrg@cygnus.com, binutils@sources.redhat.com,
	thorpej@wasabisystems.com, simonb@wasabisystems.com
Subject: Re: [PATCH] Fix distinction of 32/64bit addresses in MIPS gas
Date: Thu, 06 Sep 2001 12:09:00 -0000	[thread overview]
Message-ID: <20010906120903.A1358@lucon.org> (raw)
In-Reply-To: <yov5lmjsdv14.fsf@highland.sibyte.com>

On Thu, Sep 06, 2001 at 11:38:31AM -0700, cgd@broadcom.com wrote:

> Yes, something might be a bug w.r.t. an ABI standard that nobody
> started following until 6 months ago.  But e.g. some of the changes to

That is why I said the mips ELF implementation in binutils was only
really tested on Linux/mips :-).

> binutils will cause binary compatibility for NetBSD/mips binaries,
> which have been using the old MIPS ELF ABI implemented by binutils for
> ... 3+ years.
> 
> I don't disagree that bugs need to be fixed, but some of the fixes
> will cause some groups real pain.
> 

Been there, done that. It happened quite a few times on some Linux
platforms. Sorry, I can't help on that.

> > The only mips testsuite results for gcc I can find are Irix and Linux.
> > It won't surprise me that the next release of gcc/binutils won't work
> > on NetBSD/mips, out of box.
> 
> GCC isn't relevant here, is it?  I mean, binutils is supposed to be a
> usable compiler with gcc, without gcc, and also with random
> (not-current) versions of gcc.  NetBSD is ... much less likely to
> upgrade to a new version of gcc than to a new version of binutils.

It depends on how you see it. In my view, a toolchain should at least
include binutils and gcc. They should be compatible with each other.

> The point of my message was mostly informational: i think the list
> should be aware that there are issues re: MIPS ABIs, current binutils,
> and compatibility with a system that's been using binutils to generate
> dynamically-linked MIPS ELF binaries for years.
> 

Well, it is not an excuse not to have a good implementation of the SVR4
MIPS ABI.

BTW, "make check" in binutils checks the SVR4 ELF ABI implementation on
Linux/mips. Linux/mips also has its own testsuite for the SVR4 ELF ABI
implementation in glibc. Does NetBSD/mips have similar tests?


H.J.

  reply	other threads:[~2001-09-06 12:09 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 18:26 Thiemo Seufer
2001-08-31  8:02 ` Richard Sandiford
2001-08-31  8:28   ` H . J . Lu
2001-08-31  9:17   ` Thiemo Seufer
2001-08-31  9:53     ` Geoff Keating
2001-08-31 10:31       ` Thiemo Seufer
     [not found]         ` <mailpost.999279120.2469@postal.sibyte.com>
2001-08-31 10:37           ` cgd
2001-08-31 11:46             ` Thiemo Seufer
2001-08-31 11:49               ` Ian Lance Taylor
2001-08-31 11:50               ` Ian Lance Taylor
     [not found]               ` <mailpost.999283589.5294@postal.sibyte.com>
2001-08-31 12:41                 ` cgd
2001-08-31 14:31                   ` H . J . Lu
2001-09-03 23:07                     ` cgd
2001-09-06 10:50                       ` H . J . Lu
2001-09-06 10:59                         ` cgd
2001-09-06 11:07                           ` H . J . Lu
2001-09-06 11:35                             ` Thiemo Seufer
2001-09-06 11:39                             ` cgd
2001-09-06 11:40                               ` cgd
2001-09-08 12:03                               ` Andrew Cagney
2001-09-08 16:38                                 ` Thiemo Seufer
2001-09-08 16:56                                   ` Thiemo Seufer
2001-09-06 11:57                             ` Richard Sandiford
2001-09-06 20:53                               ` Thiemo Seufer
2001-09-06 21:09                                 ` Thiemo Seufer
2001-09-06 21:12                                 ` Thiemo Seufer
2001-09-06 22:38                                   ` H . J . Lu
2001-09-06 23:11                                     ` Thiemo Seufer
2001-09-07  4:10                                 ` Richard Sandiford
2001-09-07  6:22                                   ` Thiemo Seufer
2001-09-07  7:02                                     ` Richard Sandiford
2001-09-07  8:11                                       ` Thiemo Seufer
2001-09-07  9:20                                         ` Richard Sandiford
2001-09-07  9:49                                           ` Thiemo Seufer
2001-09-06 11:14                           ` Thiemo Seufer
2001-09-06 11:08                         ` Thiemo Seufer
2001-08-31 18:22                   ` Thiemo Seufer
2001-09-03  2:57                     ` Richard Sandiford
2001-09-03 15:00                       ` Thiemo Seufer
2001-08-31 14:49               ` Andrew Cagney
2001-08-31 15:00                 ` H . J . Lu
2001-08-31 16:30                   ` Eric Christopher
2001-08-31 16:41                     ` Andrew Cagney
2001-08-31 16:46                       ` H . J . Lu
2001-08-31 17:45                         ` matthew green
2001-09-02 19:25                         ` J Grant
2001-08-31 16:44                     ` H . J . Lu
2001-08-31 17:42                       ` matthew green
2001-08-31 19:06                         ` H . J . Lu
2001-08-31 19:11                           ` matthew green
     [not found]                             ` <mailpost.999310274.17560@postal.sibyte.com>
2001-09-03 23:18                               ` cgd
2001-09-06 11:00                                 ` H . J . Lu
2001-09-06 11:38                                   ` cgd
2001-09-06 12:09                                     ` H . J . Lu [this message]
2001-08-31 18:49                     ` Thiemo Seufer
2001-08-31 17:35                   ` matthew green
2001-08-31 19:05                     ` H . J . Lu
2001-08-31 18:25                 ` Thiemo Seufer
2001-08-31 20:46                   ` Ian Lance Taylor
2001-08-31 21:04                     ` Thiemo Seufer
2001-08-31 10:04     ` Richard Sandiford
2001-08-31 10:41       ` Thiemo Seufer

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=20010906120903.A1358@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=mrg@cygnus.com \
    --cc=simonb@wasabisystems.com \
    --cc=thorpej@wasabisystems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).