From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3069 invoked by alias); 21 Mar 2012 21:46:52 -0000 Received: (qmail 2987 invoked by uid 22791); 21 Mar 2012 21:46:48 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from qmta14.emeryville.ca.mail.comcast.net (HELO qmta14.emeryville.ca.mail.comcast.net) (76.96.27.212) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Mar 2012 21:46:34 +0000 Received: from omta10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by qmta14.emeryville.ca.mail.comcast.net with comcast id oMfF1i0060cQ2SLAEMma37; Wed, 21 Mar 2012 21:46:34 +0000 Received: from up.mrs.kithrup.com ([24.4.193.8]) by omta10.emeryville.ca.mail.comcast.net with comcast id oMmZ1i0030BKwT48WMmZuC; Wed, 21 Mar 2012 21:46:34 +0000 Subject: Re: [fixincludes] Fix pthread.h failure (PR other/52626) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Mike Stump In-Reply-To: Date: Wed, 21 Mar 2012 21:46:00 -0000 Cc: Rainer Orth , gcc-patches@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <14D8C182-D730-431D-9EFE-2CA68439C79A@comcast.net> References: To: Bruce Korb X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg01459.txt.bz2 On Mar 21, 2012, at 10:16 AM, Bruce Korb wrote: > Patch welcome! I, myself, don't know what "emit DejaGnu-style > fixincludes.{sum, log} files" would mean. Rather simple... In a file called fixinclude.sum, put PASS: unique string or FAIL: unique string one per line, as many times as you want. The unique strings should be mean= ingful to you in some way, and be stable over long periods of time (no `pwd= ` or `date` in them for example). You can write a python script, a awk scr= ipt, a bash script or a c program to generate this. You can synthesize thi= s from any source you can pull from, for example, the existing testing code= or test report you might have. Bonus points if you can total passes and failures: exec >>$file echo echo "# of expected passes $(cat $file | grep 'PASS:' | wc -l)" echo "# of expected failures $(cat $file | grep 'FAIL:' | wc -l)" at the end of the file. The above by the way, will add it (/bin/sh style),= if you just create the $file. That's it, done. For example, if you just = had a single, it all worked flawlessly thing, you could do: if check-cmd; then echo "PASS: fixinclude" else echo "FAIL: fixinclude" fi and then the code above, and viola, you're done. To create the .log file, = cp fixincludes.sum fixincludes.log, if you have nothing better to do.