From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5886 invoked by alias); 17 Sep 2013 18:38:36 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 4994 invoked by uid 89); 17 Sep 2013 17:33:25 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Sep 2013 17:33:25 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r8HHXEhD031931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 Sep 2013 13:33:14 -0400 Received: from barimba (ovpn-113-63.phx2.redhat.com [10.3.113.63]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r8HHXCYA004630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Sep 2013 13:33:13 -0400 From: Tom Tromey To: Raunaq 12 Cc: David Edelsohn , Joel Brobecker , GDB Patches , Mark Kettenis , Ulrich Weigand Subject: Re: [RFA/ppc-aix] fix thread support breakage References: <20130822233234.GA13292@adacore.com> <20130823004837.GC5221@adacore.com> <20130823133415.GD5221@adacore.com> Date: Tue, 17 Sep 2013 18:38:00 -0000 In-Reply-To: (Raunaq's message of "Tue, 10 Sep 2013 15:44:19 +0530") Message-ID: <877gefz73b.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-09/txt/msg00526.txt.bz2 >>>>> ">" == Raunaq 12 writes: >> David, my intention was to run test cases for all the combinations >> that you have mentioned above. Since we use XLC (AIX native compiler) >> to compile the test cases, the entire test bucket does not run very >> smoothly. I guess this supplies a future to-do list :-) >> In fact it is a very cumbersome process. So the test failures would >> have been over looked by me. The standard thing to do is run the test suite twice, once before your patch and once after, and compare the results. Tom