From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20677 invoked by alias); 6 Aug 2017 14:35:52 -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 18363 invoked by uid 89); 6 Aug 2017 14:35:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:1803, D*comcast.net, donate, family X-HELO: mail-vk0-f45.google.com Received: from mail-vk0-f45.google.com (HELO mail-vk0-f45.google.com) (209.85.213.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 06 Aug 2017 14:35:49 +0000 Received: by mail-vk0-f45.google.com with SMTP id g189so18715975vke.5 for ; Sun, 06 Aug 2017 07:35:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=SjUqIXmk1bygGY+VUs3ZvW7pf4pXdZuuNy9fqtEe4II=; b=jM4ZkIv9ffbmghFmILX7F0hDcyyLb249bLysyFF1eMdc3y6+iLZ6oG5gHqiMky2VcO of6w1helNutFo/vMd7DEKYN7vn3a/GRtGll+T5wAC7Z/zQrqQ7c2oV9kIAza9bxS+nP8 8qOdOqZcN3lUxQJe5UcInBqjzIEkAlyZUrKC+pqd7JKNdb+MVw4R2XDbMo9rR6waULiz ATv5JOaxyd2WeGZgOD7VMB1oTdWTq9Ct5r2EuyaWNArIs15SNx/q+jx2d25zo+pxAPh9 K/IzbAFykLaY6sU9CmKwQboffnTwdxedidATHS/RtqAOvivoIwV0Rwq/2gxVCtRDKSU+ 7l7Q== X-Gm-Message-State: AHYfb5ihWtFQNMCDbBgyjBhjEU0h02xGV+bv+K5JJxtbhI1U2/1+tZVC yRQAbbgt2lgYXvSnRHVTwuydTOS7eg== X-Received: by 10.31.230.67 with SMTP id d64mr5558411vkh.187.1502030147286; Sun, 06 Aug 2017 07:35:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.96.8 with HTTP; Sun, 6 Aug 2017 07:35:46 -0700 (PDT) In-Reply-To: <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> <09790BCE-0316-42C6-95DB-ADB75B0BD99F@comcast.net> From: Iain Buclaw Date: Sun, 06 Aug 2017 14:35:00 -0000 Message-ID: Subject: Re: [PATCH 0/2] Python testcases to check DWARF output To: Mike Stump Cc: Pierre-Marie de Rodat , Richard Biener , GCC Patches Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00459.txt.bz2 On 4 August 2017 at 00:23, Mike Stump wrote: > On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat = wrote: >> 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 testsui= te run. The problem is, for the work required, it's cheaper to do the work= once to cut over to a new language. I'd rather switch to some other langu= age that can come closer to the speed of compiled C code, yet in the script= ing family. I don't have a pointer to a better solution than python at thi= s time. I'd not be opposed to switching to python, it should be faster, ju= st as safe, a bit easier for new people to code in, and more people who kno= w it and use it. I think python is funner to code in than tcl. Cutting th= e entire testsuite over at once, might well be more than any one person can= contribute, but, we could cut over subtrees, as people donate time; if peo= ple want to go in that direction. This can't be a 1 person decision, but r= ather a consensus building type decision. What do others think? > Sounds good to me. Having recently done quite a bit of writing in tcl for the D testsuite recently, there are certainly many gotchas that I ran into. Not sure whether you would rather take an existing testing framework, or write one internally, but I can imagine something that makes heavy use of python decorators for the simple cases.