Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Move DJGPP/go32 bits to their own tdep file
Date: Wed, 12 Apr 2017 14:26:00 -0000	[thread overview]
Message-ID: <df4b03db-87a9-f706-b0c5-bf6ef5442d29@redhat.com> (raw)
In-Reply-To: <f0eb61e9-3726-5edd-6e30-67c69bb03d2f@redhat.com>

On 04/12/2017 03:07 PM, Pedro Alves wrote:
> On 04/12/2017 02:47 PM, Eli Zaretskii wrote:
>>> 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?  
> 
> Because incremental progress.

Specifically, the "trouble finding djgpp bits" I'm referring to
happened after you pointed me that djgpp needed a tweak too:

 https://sourceware.org/ml/gdb-patches/2017-03/msg00538.html

At first, I didn't see a tdep file and so I thought that I'd have
to add one, and maybe come up with a djgpp arch sniffer.  It took
me a few minutes to realize that we already have go32-specific
tdep bits in the generic i386 file.  So that's my only
motivation -- exactly to make it easier to spot the djgpp bits
quicker.  There's no other rationale behind this.  If I'll have to
go do more things to other ports to get this in, I'm afraid I'll
just drop the patch, because _I_ will have learned about them and
know next time where to look.

Thanks,
Pedro Alves


  reply	other threads:[~2017-04-12 14:26 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
2017-04-12 14:07   ` Pedro Alves
2017-04-12 14:26     ` Pedro Alves [this message]
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=df4b03db-87a9-f706-b0c5-bf6ef5442d29@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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