Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb@sources.redhat.com
Subject: Re: prgregset_t vs gdb_gregset_t on Linux: not the same!
Date: Mon, 11 Jun 2001 09:24:00 -0000	[thread overview]
Message-ID: <20010611092412.A27338@nevyn.them.org> (raw)
In-Reply-To: <3B24CC3B.8070407@cygnus.com>

On Mon, Jun 11, 2001 at 09:48:43AM -0400, Andrew Cagney wrote:
> > #ifndef TM_MIPSLITTLELINUX_H
> > #define TM_MIPSLITTLELINUX_H
> > 
> > #define TARGET_BYTE_ORDER LITTLE_ENDIAN
> > 
> > #include "mips/tm-linux.h"
> 
> 
> both the little and big endian GNU/Linux/MIPS targets should use a 
> single config/mips/tm-linux.h file.  The code no longer needs to define 
> TARGET_BYTE_ORDER.

Thanks, so I see.

> With regard to #include "tm-linux.h", I'd mimic *bsd.  That way it is 
> clear exactly what is going on.  Regardless of the semantics of "" vs <>.

Mimic *bsd in what?  In GDB, the only BSD headers I see under config/
are *-nbsd.h, and those have the same problem we do...

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
Monta Vista Software                              Debian Security Team


  parent reply	other threads:[~2001-06-11  9:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 13:27 Daniel Jacobowitz
2001-06-08 15:58 ` Daniel Jacobowitz
2001-06-08 22:14   ` H . J . Lu
2001-06-09 11:50     ` Mark Kettenis
2001-06-09 13:34     ` Andrew Cagney
2001-06-10  0:23       ` H . J . Lu
     [not found]         ` <Pine.SUN.3.91.1010610105519.5638E-100000@is>
2001-06-10  1:20           ` H . J . Lu
2001-06-11  6:48         ` Andrew Cagney
2001-06-11  8:58           ` H . J . Lu
2001-06-11 10:45             ` Andrew Cagney
2001-06-11  9:24           ` Daniel Jacobowitz [this message]
2001-06-11  9:45             ` H . J . Lu
2001-06-11 10:04               ` Daniel Jacobowitz
2001-06-11 10:45                 ` H . J . Lu
2001-06-09 15:23     ` Daniel Jacobowitz
2001-06-09 11:50   ` Mark Kettenis
2001-06-09 15:42     ` Daniel Jacobowitz

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=20010611092412.A27338@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --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