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 14:45:00 -0000 [thread overview]
Message-ID: <837f2pk7kq.fsf@gnu.org> (raw)
In-Reply-To: <df4b03db-87a9-f706-b0c5-bf6ef5442d29@redhat.com> (message from Pedro Alves on Wed, 12 Apr 2017 15:25:56 +0100)
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 12 Apr 2017 15:25:56 +0100
>
> >> 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.
It's fine with me if you decide to make only that change. I just
think that if you had this difficulty with go32 bits, someone else
might have the same difficulty with SVR4 bits. That's why I wrote
what I wrote.
next prev parent reply other threads:[~2017-04-12 14:45 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
2017-04-12 14:45 ` Eli Zaretskii [this message]
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=837f2pk7kq.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