Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ac131313@cygnus.com, msnyder@redhat.com,
	gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Mon, 22 Apr 2002 03:55:00 -0000	[thread overview]
Message-ID: <200204221054.LAA05229@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 19 Apr 2002 19:44:17 PDT." <20020419.194417.101826241.davem@redhat.com>

>    From: Andrew Cagney <ac131313@cygnus.com>
>    Date: Fri, 19 Apr 2002 22:46:23 -0400
>    
>    How does this Kernel, for instance, differentate between a GNU/Linux 
>    sparc binary and a Solaris binary when doing emulation?
> 
> I'm going to delete the Solaris binary support any day now as an
> aside.
> 
> The two binaries look identical, the both look like elf32_sparc.
> I don't know how many times I can say this.
> 
> "The binaries look identical, but we screwed up on Sparc/Linux
>  a long time ago and the long double type is 8 bytes instead of
>  the ABI mandated 16 bytes.  We are in no position to change this
>  with the amount of existing binaries out there."
> 
> There is no distinguising characterstic in the elf header nor anywhere
> else.

I'm sticking my nose in here where I probably don't know all the facts, so 
please excuse me if I'm barking up the wrong tree...

glibc does provide a note in the executable, which as I understand it, 
will differ between Linux and Solaris.  Can you not assume that if the 
note is missing entirely that you have a Sun/Solaris system and that if it 
is present you can use it to determine the OS and hence the ABI?

See glibc/abi-tags and glibc/csu/abi-note.S

R.


  parent reply	other threads:[~2002-04-22 10:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 14:54 David S. Miller
2002-04-19 18:37 ` Michael Snyder
2002-04-19 18:43   ` David S. Miller
2002-04-19 18:55   ` David S. Miller
2002-04-19 19:13     ` Andrew Cagney
2002-04-19 19:16       ` David S. Miller
2002-04-19 19:18       ` David S. Miller
2002-04-19 19:46         ` Andrew Cagney
2002-04-19 19:53           ` David S. Miller
2002-04-20 19:01             ` David S. Miller
2002-04-20 19:13               ` Jason R Thorpe
2002-04-20 19:44                 ` Andrew Cagney
2002-04-20 20:06               ` Andrew Cagney
2002-04-20 20:18                 ` David S. Miller
2002-04-20 21:24                   ` Jason R Thorpe
2002-04-20 21:32                     ` David S. Miller
2002-04-20 23:41                       ` Andrew Cagney
2002-04-22  9:24               ` Elena Zannoni
2002-04-22  3:55             ` Richard Earnshaw [this message]
2002-04-22  4:09               ` David S. Miller
2002-04-19 19:55           ` David S. Miller
2002-04-20 10:00     ` Jason R Thorpe
2002-04-20 17:59       ` David S. Miller
2002-04-20 19:04         ` Jason R Thorpe
2002-04-20 19:19           ` David S. Miller
2002-04-20 19:24             ` Jason R Thorpe
2002-04-20 19:26               ` David S. Miller
2002-04-20 20:32               ` [RFA] Sparc OS abi gdbarch init (was Re: [RFA] Sparc/Linux fixes part 1) David S. Miller

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=200204221054.LAA05229@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --cc=davem@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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