From: Elena Zannoni <ezannoni@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: fnasser@cygnus.com, cagney@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Remove unused synchronous code
Date: Tue, 20 Mar 2001 12:29:00 -0000 [thread overview]
Message-ID: <15031.48545.653713.555707@kwikemart.cygnus.com> (raw)
In-Reply-To: <7263-Sat02Dec2000100947+0200-eliz@is.elta.co.il>
Hi, I am going through a list of pending e-mails.
(yes, I have been out of the loop for a while.)
Eli has a point.
I would like to close this issue and leave things as they are
for the 5.1 release.
We should revisit this after 5.1 is out/branched.
OK?
Andrew?
Thanks
Elena
Eli Zaretskii writes:
> > Date: Fri, 01 Dec 2000 16:30:05 -0500
> > From: Fernando Nasser <fnasser@cygnus.com>
> >
> > The new event loop has been the default since 1999-06-23. This is
> > almost 1 1/2 yrs.
>
> I don't think it's correct to measure time since the introduction of
> the feature into the CVS. I think we need to measure since the first
> official release which made it the default, since that's when the
> users really see it.
>
> Correct me if I'm wrong, but I think that GDB 5.0 was the first
> official release that used the event loop as the default. GDB 5.0 was
> released in May 2000, which is only 6 months ago.
>
> In addition, DJGPP users only got a precompiled binary a few weeks
> ago (my fault), so they only now begin using it en masse.
>
> I think that removing the fallback after a single release is a too
> short notice. I think we should keep it for at least one more
> version. Please keep in mind that the async code is modeled on Unix
> and GNU/Linux systems; other platforms are using emulations of
> `select' and related facilities, and the quality of those emulations
> might vary...
>
> > It happens that the provisions for fall-back (run synchronously) are
> > getting in the way, making the code illegible
>
> Perhaps we could discuss the specific problems with retaining the old
> code, and find interim solutions for them that won't require excessive
> labor.
>
> > and requiring
> > duplicate efforts (you should still make sure that the old way works
> > -- have you tested with --noasync after applying your patches?).
>
> Perhaps the test suite should be run with --noasync as well as without
> it?
next parent reply other threads:[~2001-03-20 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A28185D.D114FFF4@cygnus.com>
[not found] ` <7263-Sat02Dec2000100947+0200-eliz@is.elta.co.il>
2001-03-20 12:29 ` Elena Zannoni [this message]
2001-03-20 12:38 ` Fernando Nasser
[not found] <5m8zpzkeir.fsf@jtc.redback.com>
2001-03-21 2:08 ` Todd Whitesel
2001-03-21 7:05 ` Elena Zannoni
[not found] <15031.47958.387059.980177@kwikemart.cygnus.com>
[not found] ` <Pine.SUN.3.91.1010321120432.24397V-100000@is>
[not found] ` <15032.49809.72980.803946@kwikemart.cygnus.com>
2001-03-24 12:34 ` Eli Zaretskii
2001-03-25 11:18 ` Elena Zannoni
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=15031.48545.653713.555707@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=cagney@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sources.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