Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: "David S. Miller" <davem@redhat.com>
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Fri, 19 Apr 2002 19:46:00 -0000	[thread overview]
Message-ID: <3CC0D67F.5060504@cygnus.com> (raw)
In-Reply-To: <20020419.190949.100077712.davem@redhat.com>

>  The value of long double can be set at run time by examining information 
>    provided by the BFD.  ARM does this for the ABI, MIPS this for almost 
>    everything.
>    
> I don't see mips-tdep.c using bfd information in it's one and only
> call to set_gdbarch_long_double_bit(), what am I overlooking?

``almost everything''?

>  From: Andrew Cagney <ac131313@cygnus.com>
> Date: Fri, 19 Apr 2002 22:13:05 -0400
>    
>    The value of long double can be set at run time by examining information 
>    provided by the BFD.  ARM does this for the ABI, MIPS this for almost 
>    everything.
> 
> I see what MIPS is doing, it does it for other type.
> 
> But this isn't going to help my long double case on
> sparc, the BFD information is going to look identical.
> 
> It's elf_sparc 32-bit, but under Linux long double's
> are 8 bytes, and that's all she wrote. :-)

The BFD is the starting point, from there you can root around in all 
sorts of nasty places.  .note sections, symbols, ....

How does this Kernel, for instance, differentate between a GNU/Linux 
sparc binary and a Solaris binary when doing emulation?

Andrew


  reply	other threads:[~2002-04-20  2:46 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 [this message]
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
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=3CC0D67F.5060504@cygnus.com \
    --to=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