public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@adacore.com, ssbssa@yahoo.de, bernd.edlinger@hotmail.de,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix build issues with mingw toolchain
Date: Mon, 13 May 2024 18:12:58 +0100	[thread overview]
Message-ID: <aeb49d16-7f87-4179-a54b-03537d806a16@palves.net> (raw)
In-Reply-To: <868r0dyb91.fsf@gnu.org>

On 2024-05-13 16:36, Eli Zaretskii wrote:
>> Date: Mon, 13 May 2024 15:21:16 +0100
>> Cc: tromey@adacore.com, ssbssa@yahoo.de, bernd.edlinger@hotmail.de,
>>  gdb-patches@sourceware.org
>> From: Pedro Alves <pedro@palves.net>
>>
>> On 2024-05-11 07:20, Eli Zaretskii wrote:
>>>> From: Pedro Alves <pedro@palves.net>
>>
>>> Cygwin and MSYS2 indeed won't run on older Windows, but programs they
>>> create still can, if built with caution and don't use any APIs from
>>> later versions without run-time checking (like we do).
>>>
>>>> It's quite likely that number of people really really using
>>>> current GDB (for anything productive) on older Windows versions is very reduced,
>>>> if not approaching zero.
>>>
>>> Emacs still supports Windows XP (and even older versions), so it is
>>> important for us to be able to run the latest GDB on XP.
>>>
>>
>> OOC, is there a reason GDB versions other than the latest wouldn't work for
>> that?
> 
> Well, the future support for non-stop on Windows is one reason.  Emacs
> on Windows uses several threads, as you may or may not know.

That feature will only work on Windows 10 and above, so newer GDB will
work the same as older GDB on WinXP.

> 
> Newer GCC versions used to compile Emacs are another reason: as DWARF
> info emitted by GCC is enhanced, we need newer versions of GDB to
> support that.

OK, I can see that.

> 
> More generally, as long as GDB doesn't _have_ to drop XP, i.e., as
> long as keeping it doesn't place a too significant burden on GDB
> maintenance, I think we should not deliberately break it.

Agreed.

> 
>> I don't plan on proposing bumping the minimal supported version currently,
>> as I don't recall it blocking anything, but I would like to understand that
>> constraint better, for if/when the time comes.
> 
> I hope I provided at least some rationale for my opinions.  (They are
> not constraints, not unless the entire team agrees that this is our
> official policy.)
> 

Thanks for the clarification.

  reply	other threads:[~2024-05-13 17:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  5:58 Bernd Edlinger
2024-05-06 14:57 ` Tom Tromey
2024-05-06 17:09   ` Bernd Edlinger
2024-05-06 20:18     ` Tom Tromey
2024-05-07 10:59       ` Hannes Domani
2024-05-10 17:24         ` Tom Tromey
2024-05-10 17:32           ` Eli Zaretskii
2024-05-10 17:41           ` Eli Zaretskii
2024-05-10 19:03           ` Pedro Alves
2024-05-11  6:20             ` Eli Zaretskii
2024-05-13 14:21               ` Pedro Alves
2024-05-13 15:36                 ` Eli Zaretskii
2024-05-13 17:12                   ` Pedro Alves [this message]
2024-05-13 18:45                 ` Tom Tromey
2024-05-14 14:20                   ` Pedro Alves
2024-05-14 17:02                     ` Eli Zaretskii
2024-05-14 18:47                       ` Pedro Alves
2024-05-14 19:19                         ` Eli Zaretskii
2024-05-11 10:55           ` Hannes Domani
2024-05-13 13:45             ` Tom Tromey
2024-05-10 17:39       ` Eli Zaretskii
2024-05-13 13:48         ` Tom Tromey
2024-05-10 17:37     ` Eli Zaretskii
2024-05-10 19:36       ` Bernd Edlinger
2024-05-11  6:18         ` Eli Zaretskii

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=aeb49d16-7f87-4179-a54b-03537d806a16@palves.net \
    --to=pedro@palves.net \
    --cc=bernd.edlinger@hotmail.de \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    --cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).