Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDBserver ports cleanup
Date: Wed, 13 May 2020 13:01:21 +0100	[thread overview]
Message-ID: <6046157a-80fc-95d1-ff06-0892343c6f34@redhat.com> (raw)
In-Reply-To: <CAPTJ0XHc67QtPaZeJ3fGj6pqDqzGxUTcfMRoTVOGMA8O3EW2Vw@mail.gmail.com>

On 5/12/20 9:26 PM, Christian Biesinger via Gdb-patches wrote:
> On Tue, May 12, 2020 at 11:48 AM Simon Marchi via Gdb-patches

>> About Windows support for ARM, I don't really know about it.  I think that our port
>> was targeting Windows CE [2], which can probably be considered obsolete.  However,
>> Windows 10 supposedly runs on ARM [3], so it might be relevant to keep it?  I don't really
>> know if the current GDBserver code would help for that or not.  In doubt, I won't propose
>> to remove it.
> 
> If indeed the win32-arm support handles Windows 10, I think it would
> be good to keep it, but I am not sure it does -- win32-arm-low.cc does
> have these lines:
> /* Correct in either endianness.  We do not support Thumb yet.  */
> static const unsigned long arm_wince_breakpoint = 0xe6000010;
> #define arm_wince_breakpoint_len 4
> 
> Note mention of WinCE. Also, I am not so familiar with Thumb but I
> believe that's widely used on ARM these days?
> 
> So my vote would be to remove this for now and if someone wants to
> revive it there's the git history.
win32-arm support in gdbserver is only for Windows CE.  I was the one
who wrote it, it was the reason I got into GDB hacking in the first
place.  :-)  There was no Windows for ARM back then.  

I don't object removing it.  I haven't built a compiler or gdbserver
for WinCE in years, and I doubt anyone else has^W^W^W^W^W^W^W^W^W^W^W^W
Wow, I just found out that someone forked my old cegcc project, and
updated it based on a much more modern GCC:
https://max.kellermann.name/projects/cegcc/
I had no idea.  Look like he has some local GDB in his github, though
dated from 2016/2018.

If you do remove it, then you'll want to remove all the code guarded under
_WIN32_WCE in win32-low.cc, and also wincecompat.c.  There's also
ARM WinCE support on the GDB side, in arm-wince-tdep.c.

I'm not sure there's that much salvageable for an eventual Windows for ARM
port.  For example, Windows for ARM is strictly Thumb-2, while I don't recall
ever considering Thumb-2 back then.  WinCE was FPA, I believe, while Windows
for ARM is VFP.  The ABIs are just different, and WinCE is weird beyond belief.
(no "errno", no concept for "current directory", etc.).

Other than nostalgia for being what got me into GDB, I really won't miss it
myself.

Thanks,
Pedro Alves



  reply	other threads:[~2020-05-13 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 16:47 Simon Marchi
2020-05-12 20:26 ` Christian Biesinger
2020-05-13 12:01   ` Pedro Alves [this message]
2020-05-13 14:45     ` Simon Marchi
2020-05-13 15:01       ` Pedro Alves
2020-05-13 12:37   ` Luis Machado
2020-05-13 13:11     ` Alan Hayward
2020-05-13 14:47       ` Simon Marchi
2020-05-13 18:36 ` Joseph Myers
2020-05-13 18:40   ` Simon Marchi

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=6046157a-80fc-95d1-ff06-0892343c6f34@redhat.com \
    --to=palves@redhat.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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