From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.1 Release
Date: Mon, 15 Apr 2002 15:06:00 -0000 [thread overview]
Message-ID: <10204152158.AA09645@vlsi1.ultra.nyu.edu> (raw)
There's also the problem that some people don't seem to want to invest
very much effort to fix problems on platforms they don't use, even
when it's clear they created the problem. That's a social issue.
Not completely. In some cases I recall, what happened was that a patch
triggered a latent bug on some machine. Fixing that can often require
quite intimiate knowlege of the structure of that machine and/or port,
so it's not just a matter of unwillingness to fix it but it can often be
inability. I see this as a serious problem because from a project point
of view we don't want to let a useful and totally correct improvement not be
applied because of some latent bug in a not-widely-used target. But that
doesn't mean we want to break that target either. I don't think there's a
good solution to this problem.
next reply other threads:[~2002-04-15 22:01 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 15:06 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 11:37 Mark Mitchell
2002-05-05 15:00 ` Florian Weimer
2002-05-06 3:24 ` Andreas Schwab
2002-05-06 7:54 ` Mark Mitchell
2002-05-06 7:57 ` Andreas Schwab
2002-05-06 15:16 ` Mark Mitchell
2002-05-07 1:43 ` Andreas Schwab
2002-04-14 10:34 Robert Dewar
2002-04-13 13:51 Robert Dewar
2002-04-12 18:51 Mark Mitchell
2002-04-13 2:21 ` Neil Booth
2002-04-13 7:50 ` Toon Moene
2002-04-13 8:40 ` Tim Prince
2002-04-13 23:07 ` Bryce McKinlay
2002-04-14 17:04 ` David Edelsohn
2002-04-15 17:19 ` David O'Brien
2002-04-15 18:02 ` David Edelsohn
2002-04-16 17:06 ` Marc Espie
2002-04-22 19:44 ` David O'Brien
2002-04-22 20:11 ` Bryce McKinlay
2002-04-23 11:04 ` David O'Brien
2002-04-23 16:15 ` Bryce McKinlay
2002-04-22 22:25 ` Kaveh R. Ghazi
2002-04-14 1:33 ` H . J . Lu
2002-04-16 17:00 ` Marc Espie
2002-04-17 2:08 ` Gerald Pfeifer
2002-05-17 5:42 ` Marc Espie
2002-05-17 16:19 ` Loren James Rittle
2002-05-17 17:07 ` David O'Brien
2002-05-17 17:08 ` Marc Espie
2002-04-13 13:18 ` Tom Tromey
2002-04-14 6:59 ` Jason Merrill
2002-04-14 7:25 ` Andreas Jaeger
2002-04-14 8:16 ` Jason Merrill
2002-04-15 10:56 ` Geoff Keating
2002-04-15 11:19 ` H . J . Lu
2002-04-16 15:16 ` mark
2002-04-16 15:23 ` H . J . Lu
2002-04-17 2:54 ` Andreas Schwab
2002-04-15 11:36 ` Andreas Jaeger
2002-04-15 11:37 ` Joe Buck
2002-04-15 13:13 ` Geoff Keating
2002-04-15 12:00 ` Andreas Jaeger
2002-04-15 12:01 ` Mark Mitchell
2002-04-15 12:13 ` Michael Matz
2002-04-15 12:22 ` Mark Mitchell
2002-04-15 14:52 ` Geoff Keating
2002-04-15 15:01 ` Mark Mitchell
2002-04-03 23:20 John David Anglin
2002-04-03 2:38 Reichelt
2002-04-03 13:21 ` Mark Mitchell
2002-04-02 14:38 Mark Mitchell
2002-04-02 14:47 ` Tom Tromey
2002-04-03 15:06 ` Phil Edwards
2002-04-03 16:08 ` Joe Buck
2002-04-03 17:57 ` Phil Edwards
2002-04-04 10:17 ` Mark Mitchell
2002-04-09 9:48 ` Joe Buck
2002-04-09 10:44 ` Benjamin Kosnik
2002-04-09 11:35 ` Gabriel Dos Reis
2002-04-10 2:37 ` Mark Mitchell
2002-04-10 7:59 ` Joe Buck
2002-04-10 8:17 ` Gabriel Dos Reis
2002-04-10 8:22 ` Joe Buck
2002-04-10 10:14 ` Mark Mitchell
2002-04-10 11:39 ` Benjamin Kosnik
2002-04-10 11:47 ` Paolo Carlini
[not found] ` <flwuvfqrme.fsf@jambon.cmla.ens-cachan.fr>
2002-04-12 5:12 ` Paolo Carlini
2002-04-10 13:01 ` Gabriel Dos Reis
2002-04-11 6:02 ` Joe Buck
2002-04-11 14:58 ` Gabriel Dos Reis
2002-04-15 17:51 ` Gabriel Dos Reis
2002-04-15 19:36 ` Gabriel Dos Reis
2002-04-15 19:43 ` Mark Mitchell
2002-04-15 20:03 ` Gabriel Dos Reis
2002-04-06 7:47 ` Jason Merrill
2002-04-10 10:17 ` Janis Johnson
2002-04-10 10:24 ` Mark Mitchell
2002-04-10 10:35 ` Christian Jönsson
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=10204152158.AA09645@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).