Re: [RFC/WIP PATCH 03/14] Flip to set target-async on by default

[Tom Tromey <tromey@redhat.com>]

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Pedro> This flips "set target-async" to default to on.  I see no failures
Pedro> left with this on x86_64-linux, and there used to be none either
Pedro> against gdbserver, but I haven't tried recently.  One thing left to
Pedro> decide is what to do with MI.  If the frontend never flips async
Pedro> explicitly, should we bother to emulate sync MI output, or can we
Pedro> expect that all frontends can and should cope with async on by default
Pedro> by now?

First, I want us to make target-async default to on.  I have a few other
defaults I'd like to flip, too.

For the MI part, I think we should reach out to the "main" MI consumers
out there -- and by "main" I just mean ones that we know of and that
seem to be maintained -- and ask.  (It seems like it would be good to
have some open channel for doing this more regularly.)

Actually, come to think of it, instead of asking, we should probably
just announce the change and see what kind of push-back we get.

In the extreme we can make the next release "8.0" as a way of
advertising that we're making bigger changes.

Tom