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:13:00 -0000	[thread overview]
Message-ID: <3CC0CEB1.9080106@cygnus.com> (raw)
In-Reply-To: <20020419.184709.103241554.davem@redhat.com>

>  From: Michael Snyder <msnyder@redhat.com>
> Date: Fri, 19 Apr 2002 18:25:32 -0700
> 
>    "David S. Miller" wrote:
>    > 32-bit Sparc under Linux does not have a 16-byte long double,
>    > this causes testsuite failures.  Fix this by providing a
>    > SPARC_TARGET_LONG_DOUBLE_BYTES the OS specific target headers
>    > can override.
>    
>    The idea is sound, but the implementation is not very 
>    multi-arch-ish.  Is there a runtime way to do this, 
>    rather than by using a macro?  The whole purpose of
>    multi-arch is that these decisions get made at runtime.
> 
> Some more commentary, just to be absolutely clear...
> 
> Note that this is an OS-specific setting, and the current
> multi-arch code does not lend itself to anything other
> than cpu target gdbarch inits.

sizeof(long double) is a property of the ABI not the OS.

> If GDB provided a framework whereby I could install an os-specific
> gdbarch_init, I'd be more than happy to implement this in the
> holy-grail-multi-arch way you want me to.
> 
> Look, I'll stick around long after this change is installed so
> when the facility is there, I will convert this long double
> stuff to use it and the macros will basically disappear from the
> sparc headers. :-)

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.

enjoy,
Andrew






  reply	other threads:[~2002-04-20  2:13 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 [this message]
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
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=3CC0CEB1.9080106@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