public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mmitchell@usa.net>
To: Joe Buck <jbuck@synopsys.com>
Cc: hjl@lucon.org, egcs@cygnus.com
Subject: Re: An important patch for egcs 1.0.1
Date: Mon, 16 Feb 1998 16:56:00 -0000	[thread overview]
Message-ID: <199802161433.OAA25973@quickstep.stanford.edu> (raw)
In-Reply-To: <199802162200.OAA11328@atrus.synopsys.com>

>>>>> "Joe" == Joe Buck <jbuck@Synopsys.COM> writes:

    >> It's not obvious to me that just because 1.0.1 miscompiles
    >> glibc 2.x the long double fix can't wait for 1.1.

    Joe> HJ just sent the patch, and it seems short, and furthermore,
    Joe> he says it's been in the snapshots since before egcs-1.0.1.
    Joe> So why the resistance?

I'm afraid I didn't make myself clear.  In the mail you refer to, I
also wrote:

    However, if the fixes are simple, my points may be moot, and I
    don't pretend to pass judgement on the fixes themselves.  So, this
    is not an argument not to put the fixes in; only one about how we
    should determine what fixes are to go in.

I was not, therefore, trying to "resist" any particular fix.  You'll
note that I explicitly express ignorance about the particular patch in
question.

However, I stand by my statement that the bugs we fix for 1.0.2 should
be: 

  truly egregious and horrible bugs that can be fixed with very simple
  changes

The statement you quoted was meant to imply that the mere fact that
glibc cannot be compiled with the egcs release branch does not
immediately imply (in my opinion) that we are not ready for that
release.  If however, you find that bug very disturbing (and obviously
many people do!) and you believe that HJs fixes are simple (and
obviously many people do!), then I think it's clear that the fixes
should go in.  

I really didn't mean to create any controversy, or to criticize any
patches (I haven't even looked at them!).  I simply meant to caution
all of us against spending too much time messing with 1.0.2; releasing
1.1 will fix many more problems and add many more features.  I bet we
all agree; the only question is where to draw the line on 1.0.2.  I
advocate drawing the line soon, even if it means that some programs
will not work.  Again, that's not a specific comment on this
*particular* program (glibc) or the *particular* patch (HJ's long
double repair).

-- 
Mark Mitchell		mmitchell@usa.net
Stanford University	http://www.stanford.edu


  parent reply	other threads:[~1998-02-16 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-15 11:33 Daniel Egger
1998-02-15 11:41 ` H.J. Lu
1998-02-15 13:42   ` Mark Mitchell
1998-02-15 17:27     ` Michael Neuffer
1998-02-16 14:21     ` Joe Buck
1998-02-16 14:21       ` H.J. Lu
1998-02-16 16:56       ` Mark Mitchell [this message]
1998-02-16 18:19         ` Joe Buck
1998-02-16 18:43           ` Mark Mitchell
1998-02-16 21:16       ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1998-02-15 13:42 Daniel Egger
     [not found] <34E2AFA6.F4E316C@erols.com>
1998-02-12 20:07 ` H.J. Lu

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=199802161433.OAA25973@quickstep.stanford.edu \
    --to=mmitchell@usa.net \
    --cc=egcs@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=jbuck@synopsys.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).