Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Move DJGPP/go32 bits to their own tdep file
Date: Wed, 12 Apr 2017 13:47:00 -0000	[thread overview]
Message-ID: <83bms1ka9s.fsf@gnu.org> (raw)
In-Reply-To: <1492003875-25394-1-git-send-email-palves@redhat.com> (message	from Pedro Alves on Wed, 12 Apr 2017 14:31:15 +0100)

> From: Pedro Alves <palves@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Wed, 12 Apr 2017 14:31:15 +0100
> 
> I posit that this makes them easier to find.
> 
> The other day while working on the wchar_t patch, I had a bit of
> trouble finding the DJGPP/go32 tdep bits.  My initial reaction was
> looking for a go32-specific tdep file, but there's none.

Thanks, but why single out go32?  The comment in i386-tdep.c says:

  /* There are a few i386 architecture variants that differ only
     slightly from the generic i386 target.  For now, we don't give them
     their own source file, but include them here.  As a consequence,
     they'll always be included.  */

If we are going to have a separate tdep file for such architectures,
let's do it for SVR4 as well.

P.S. How come functions and other symbols are looked for via file
names, and not via TAGS?


  reply	other threads:[~2017-04-12 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 13:31 Pedro Alves
2017-04-12 13:47 ` Eli Zaretskii [this message]
2017-04-12 14:07   ` Pedro Alves
2017-04-12 14:26     ` Pedro Alves
2017-04-12 14:45       ` Eli Zaretskii
2017-04-12 14:57         ` Pedro Alves
2017-04-12 15:32           ` Pedro Alves
2017-04-12 14:42     ` Eli Zaretskii
2017-04-12 14:46       ` Pedro Alves
2017-04-12 14:58         ` Eli Zaretskii
2017-04-12 15:02           ` Pedro Alves

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=83bms1ka9s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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