From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54764 invoked by alias); 3 Aug 2017 22:23:47 -0000 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 Received: (qmail 54752 invoked by uid 89); 3 Aug 2017 22:23:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=firm, H*m:0316, donate, heard X-HELO: resqmta-po-07v.sys.comcast.net Received: from resqmta-po-07v.sys.comcast.net (HELO resqmta-po-07v.sys.comcast.net) (96.114.154.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 03 Aug 2017 22:23:45 +0000 Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-07v.sys.comcast.net with ESMTP id dOWedDkDL5ingdOWudbaa8; Thu, 03 Aug 2017 22:23:44 +0000 Received: from up.mrs.kithrup.com ([24.4.193.248]) by resomta-po-04v.sys.comcast.net with SMTP id dOWtdbhGB5XlFdOWudg7R4; Thu, 03 Aug 2017 22:23:44 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [PATCH 0/2] Python testcases to check DWARF output From: Mike Stump In-Reply-To: <55c21fe5-da33-74d7-fe42-c6735fd50e26@adacore.com> Date: Thu, 03 Aug 2017 22:23:00 -0000 Cc: Richard Biener , GCC Patches Content-Transfer-Encoding: quoted-printable Message-Id: <09790BCE-0316-42C6-95DB-ADB75B0BD99F@comcast.net> References: <20170726160040.6516-1-derodat@adacore.com> <8EF1EAAC-B956-4214-A707-EE692659F428@comcast.net> <55c21fe5-da33-74d7-fe42-c6735fd50e26@adacore.com> To: Pierre-Marie de Rodat X-CMAE-Envelope: MS4wfPipir8ZBLjPkerM29p/IxgXKlvwFomg/IbzKCOesYkPQ5DErc7D/jI6PTdTNXyhh6dQJkmZr1Jc9w3sMNUaZbIyA42nDpXvWskyNNNxofba+6R1MIEC MLFcnse0iVTFVuLZLSpZHgiFE/IZUivChp94IAmKRlE1iCFPtNdFwztpW024Ebwd5KKFemvKCxBlf7DYhdVe0Z5EPEGMJkeCOcYEDHi6KU9Jd8kJiVDbpUps krHBwXkC3TLH8cJ1HIrg4Q== X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00349.txt.bz2 On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat wr= ote: > On 07/27/2017 09:52 AM, Richard Biener wrote: >>> I'm fine with the direction if a reviewer wants to go in that >>> direction. I wish python didn't have a built-in speed penalty, >>> that's the only downside I don't like about it. Aside from that, >>> even switching all of the testsuite to be python based isn't a >>> terrible idea. >> But is it worse than TCL? python is likely 2x faster than tcl, if you have one instance per testsuite= run. The problem is, for the work required, it's cheaper to do the work o= nce to cut over to a new language. I'd rather switch to some other languag= e that can come closer to the speed of compiled C code, yet in the scriptin= g family. I don't have a pointer to a better solution than python at this = time. I'd not be opposed to switching to python, it should be faster, just= as safe, a bit easier for new people to code in, and more people who know = it and use it. I think python is funner to code in than tcl. Cutting the = entire testsuite over at once, might well be more than any one person can c= ontribute, but, we could cut over subtrees, as people donate time; if peopl= e want to go in that direction. This can't be a 1 person decision, but rat= her a consensus building type decision. What do others think? > Good point. Actually for Python there are ways to make it faster. If we c= an somehow manage to have a limited set of Python interpreter instances (in= stead of one per test), we could use pypy, which is very good I heard to ma= ke long running instances fast. Yes. One instance would help ensure the performance is good. I don't have= a firm grasp of startup time to know just how critical it is. Also, I don= 't have a good grasp on memory pressures that python would create, say, com= pared to how we use tcl.