public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: binutils@sources.redhat.com
Subject: Re: [PATCH] Fix bfd ABI string for MIPS
Date: Thu, 16 Aug 2001 11:10:00 -0000	[thread overview]
Message-ID: <20010816200837.W381@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <3B7BF7C9.3040306@cygnus.com>

Andrew Cagney wrote:
> > On 16 Aug 2001 03:41:48 +0200, Thiemo Seufer wrote:
> > 
> >> Hi All,
> >> 
> >> currently bfd returns for the MIPS ABI string "N32" for every ELF
> >> object with header flag EF_MIPS_ABI2 set and "64" for every ELF
> >> object which is 64bit.

First of all, sorry for this bad description. It's not that bfd
returns this string to an client, it's use is internal to
elf32-mips.c. Having a closer look, it's in fact only used for
an error message about modules with incompatible ABI.

> >> This means E_MIPS_ABI_O64 and E_MIPS_ABI_EABI64 are named wrongly
> >> as "64", and an object with EF_MIPS_ABI2 and arbitrary other flags
> >> set is also wrongly called "N32".
> >> 
> >> The patch below fixes this.
> > 
> > I think this may have side effects.  How did you test this? gcc and gdb?
> > 
> > -eric
> > 
> 
> Yes, I wondered the same thing.  Here, I think it doesn't have an effect 
>   on GDB. GDB grubs aound in the bits in the elf header when determining 
> the ABI.  However, caution is definitly advised.

Sorry again. It definitely has no side effect except of putting out
the correct ABI names in the error message.


Thiemo

  reply	other threads:[~2001-08-16 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15 14:40 Thiemo Seufer
2001-08-16  9:26 ` Eric Christopher
2001-08-16  9:41   ` Andrew Cagney
     [not found]     ` <20010816200837.W381@rembrandt.csv.ica.uni-stu>
2001-08-16 11:10     ` Thiemo Seufer [this message]
2001-08-24 11:57       ` Thiemo Seufer
2001-08-24 13:25         ` Eric Christopher
2001-08-24 13:39           ` Andrew Cagney
2001-08-24 13:43             ` Eric Christopher

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=20010816200837.W381@rembrandt.csv.ica.uni-stuttgart.de \
    --to=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=binutils@sources.redhat.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).