public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matt Austern <austern@apple.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Mark Mitchell <mark@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Committed] Use special-purpose hash table to speed up walk_tree
Date: Sun, 17 Oct 2004 18:45:00 -0000	[thread overview]
Message-ID: <05B05D49-2068-11D9-A3A0-000393B2ABA2@apple.com> (raw)
In-Reply-To: <200410171158.29730.stevenb@suse.de>

On Oct 17, 2004, at 2:58 AM, Steven Bosscher wrote:

> On Sunday 17 October 2004 07:51, Mark Mitchell wrote:
>> I don't think there is any such policy one way or the other.  
>> Certainly,
>> there is precedent for patches being approved offline.
>
> I know there is, and I think it's wrong.  More eyes see more
> things.
>
>
>>  Matt sent me the
>> patch, and it looked good to me.  I didn't see any reason to test it 
>> on
>> other architectures.
>
> Well, we've have some pretty serious breakage a few times in the
> past few weeks.  Already three times the cause of this breakage
> was that some patch wasn't tested on some architecture.  So I
> see lots of reasons to require better testing for patches when
> the mainlne is in stage3.
>
> Can we make it a requirement that larger patches like this should
> be tested on three platforms when the mainline is in stage3?

That may be a good idea, but bear in mind that it probably would
not have caught this problem.  I don't regularly use a platform
where pointers are 64-bit, so if I were testing this on three
platforms it probably would have been three 32-bit platforms.
If we're looking for diversity, it had probably better be
something like this: at least one non-Linux platform, at least
one non-ELF platform, at least one non-x86 platform, at least
two different word sizes.

			--Matt 

  reply	other threads:[~2004-10-17 18:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 23:22 Matt Austern
2004-10-14 23:24 ` Phil Edwards
2004-10-15  0:04   ` Matt Austern
2004-10-16 10:17 ` Jakub Jelinek
2004-10-16 10:37   ` Steven Bosscher
2004-10-17  8:30     ` Mark Mitchell
2004-10-17 10:59       ` Steven Bosscher
2004-10-17 18:45         ` Matt Austern [this message]
2004-10-18  4:19         ` Mark Mitchell
2004-10-21 21:25         ` Gerald Pfeifer
2004-10-16 10:42   ` Jakub Jelinek
2004-10-16 11:49     ` Jakub Jelinek
2004-10-16 18:29     ` Matt Austern
2004-10-16 18:35     ` Richard Henderson
2004-10-16 18:37       ` Jakub Jelinek
2004-10-16 18:51         ` Richard Henderson
2004-10-16 19:15           ` Jakub Jelinek
2004-10-17  1:11             ` Richard Henderson
2004-10-16 18:14   ` Matt Austern
2004-10-18 14:48 Richard Kenner

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=05B05D49-2068-11D9-A3A0-000393B2ABA2@apple.com \
    --to=austern@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mark@codesourcery.com \
    --cc=stevenb@suse.de \
    /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).