Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Multi-arching FLOAT_INFO
Date: Tue, 05 Feb 2002 08:52:00 -0000	[thread overview]
Message-ID: <3C600DDE.1000902@cygnus.com> (raw)
In-Reply-To: <200202051557.PAA28800@cam-mail2.cambridge.arm.com>

> + void
>> > + default_float_info (void)
>> > + {
>> > + #ifdef FLOAT_INFO
>> > + #if GDB_MULTI_ARCH
>> > + #error "FLOAT_INFO defined in multi-arch"
> 
>> 
>> 
>> Suggest #if GDB_MULTI_ARCH > GDB_MULTI_ARCH_PARTIAL
> 
> 
> But surely a multi-arch (even a partial multi-arch) should be using the 
> new function, not the old one.  I thought it was ok to be using 
> legacy-style definitions of multi-arch macros, but not to be using 
> deprecated ones (hence the error).  If that is incorrect of course, I can 
> easily change it as you suggest.


It is a compromize.  GDB_MULTI_ARCH_TM and above do what you describe. 
GDB_MULTI_ARCH_PARTIAL is intentionally lax about what it allows, only 
barfing a build when absolutly necessary.  The intention is to make the 
steps necessary before adding #define GDB_MULTI_ARCH 
GDB_MULTI_ARCH_PARTIAL as minimal as possible.  Since you've fixed the 
frame stuff, can I suggest skipping to the step where the above is defined.

Andrew


      reply	other threads:[~2002-02-05 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04  6:43 Richard Earnshaw
2002-02-04  8:33 ` Andrew Cagney
2002-02-05  2:34   ` Richard Earnshaw
2002-02-05  7:41     ` Andrew Cagney
2002-02-05  7:57       ` Richard Earnshaw
2002-02-05  8:52         ` Andrew Cagney [this message]

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=3C600DDE.1000902@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@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