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: Non-multiarched macros
Date: Fri, 01 Feb 2002 08:26:00 -0000	[thread overview]
Message-ID: <3C5AC1B2.50805@cygnus.com> (raw)
In-Reply-To: <200202011407.OAA29668@cam-mail2.cambridge.arm.com>

> The following macros are defined by the ARM and are referenced by the 
> generic code, but appear not be multi-arched.
> 
> What is supposed to happen here?
> 
> SMASH_TEXT_ADDRESS	  -- coffread.c dbxread.c dwarfread.c elfread.c
> 			     somread.c
> FLOAT_INFO		  -- infcmd.c
> VARIABLES_INSIDE_BLOCK    -- dbxread.c os9kread.c
> ELF_MAKE_MSYMBOL_SPECIAL  -- elfread.c
> COFF_MAKE_MSYMBOL_SPECIAL -- coffread.c


Anyone can convert these macros to use the multi-arch framework and 
hopefull that conversion is a straight forward afair.  Easiest way I 
know to do this is to copy a similar example.  If you're wondering what 
isn't straight forward look at mips_extra_frame_info()  (Jason Thorp 
note - this stops the Alpha being fully converted, see gdb/150 and 
gdb/149 and gdb/151).

I'd do these in parallel with other changes since throwing the 
multi-arch switch doesn't depend on these being functions.

Some suggestions.

 > SMASH_TEXT_ADDRESS	  -- coffread.c dbxread.c dwarfread.c elfread.c
 > 			     somread.c

REGISTER_BYTES_OK

 > FLOAT_INFO		  -- infcmd.c

DO_REGISTERS_INFO

need to change FLOAT_INFO -> FLOAT_INFO().

 > VARIABLES_INSIDE_BLOCK    -- dbxread.c os9kread.c

Is OS9K_VARIABLES_INSIDE_BLOCK defined?
DO_REGISTERS_INFO

 > ELF_MAKE_MSYMBOL_SPECIAL  -- elfread.c

REGISTER_BYTES_OK

 > COFF_MAKE_MSYMBOL_SPECIAL -- coffread.c

REGISTER_BYTES_OK

There was an e-mail explaining the choice somewhere (Eli, I guess it is 
time to give in and put it into the internals manual).  However, briefly:

#ifdef FOO
    FOO()
#endif

becomes

    if (FOO_P())
     FOO();

and

#ifndef FOO
#define FOO() bar()
#endif
     FOO()

becomes

     FOO()

with bar() made the default.  The main thing is to resist any temptation 
to do anything beyond a mechanical conversion.

enjoy,
Andrew


  reply	other threads:[~2002-02-01 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  6:07 Richard Earnshaw
2002-02-01  8:26 ` Andrew Cagney [this message]
2002-02-01  9:04   ` Richard Earnshaw
2002-02-01  9:08     ` Daniel Jacobowitz
2002-02-01  9:27     ` Andrew Cagney

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=3C5AC1B2.50805@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