From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48350 invoked by alias); 7 Mar 2018 16:49:46 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 47616 invoked by uid 89); 7 Mar 2018 16:49:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=rapid, frustrating, texts, click X-HELO: mail-yw0-f195.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iK/rIB/2eyWKgRU74k0yEtPV8iZOxzNCrUcKUnPXWd0=; b=PT0m5DnKDor5nzeCA3gJ/XTVHobR2V6PPJaT0UoRVGFWwh+kaT1g3UaBoRn44B4OyJ FgZo/xW3CjVWwOoPbEEPXQQxgVqZ1GFP5IC+v7h1BGVDtaUzG6m5uCnaNMu/ObKwl7OD G95DKAfBTFz7nCyIpdHF64kFNGx6aA+DKuif5Ke2phXVoK6imkeFCamyazrTJmcKF3U2 r6+vNUe5lnLTK9aiHL3DO3nDaNJpTu3KUdBd5icOpZYm9o32b01JsrgWWYzQRKxq0v7b 1LVjAiWS4VMcdb56WCGB7XHNz7+xvHulaLfe6E5k/nc/20R4KT1JGWLatsYmnN4QVw4v pKsw== X-Gm-Message-State: APf1xPAOIChfFtHZ+4bHSZpsxM8aulh9zxi5Aygq+/Tw3ogRw0kRp8wc eWUoiQch9CG2FTsiJ3NXug2tLDdLt0M= X-Google-Smtp-Source: AG47ELuGxvQMYWzX083xjggz78nDCAVsirXMOSMuCWOb7gCFooho17x46ms9oeXJ0vmJO6Ox8rIrwQ== X-Received: by 10.129.182.18 with SMTP id u18mr14457318ywh.22.1520441382375; Wed, 07 Mar 2018 08:49:42 -0800 (PST) Subject: Re: RFC: remove the "tile" architecture from glibc To: libc-alpha@sourceware.org References: <1a57be83-3349-5450-ee4f-d2a33569a728@mellanox.com> <21665e92-27d1-81c5-5959-f0893541b515@physik.fu-berlin.de> From: Adhemerval Zanella Message-ID: <5e3ee2bd-b1ca-9871-9f90-33b3ce90534d@linaro.org> Date: Wed, 07 Mar 2018 16:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <21665e92-27d1-81c5-5959-f0893541b515@physik.fu-berlin.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2018-03/txt/msg00177.txt.bz2 On 07/03/2018 13:08, John Paul Adrian Glaubitz wrote: > On 03/07/2018 05:00 PM, Joseph Myers wrote: >> No-one has posted glibc test results for 2.27 or 2.26, despite the prior >> claims of interest in keeping the glibc port. > > To be honest, I find the rapid release model for glibc a bit annoying > as a downstream. Upstream projects which adopt this model and then require > constant attention from porters cause lots of stress for the less common > architectures. There are other upstream projects that want attention as > well and at some point it just will get extremely frustrating. > > Is such a rapid release model really needed for something like a C library? My understanding it is aligns with fedora release cycle. We have the advantage of early testing based on distro userbase, but I also don't have a strong opinion to have a per year release. > > As for the testsuites: Adhemerval has gotten access from Debian to a > number of porterboxes for the various uncommon architectures, including > alpha, hppa, powerpcspe, sh4 and sparc64 and we're happy to give out > accounts to anyone interested. Btw I have added 2.26 and 2.27 tests results for alpha, hppa, sh4, sparc64, and sparcv9. The powerpspe I thought we should be covered since we had powerpc hard float and soft float, but with recent build issues I think I will add it on the loop. > > And since Debian regularly updates glibc as well, you can get most testsuite > runs also by just checking the build logs (click on the green or red texts): > >> https://buildd.debian.org/status/package.php?p=glibc&suite=sid > > Note: Testsuites for sh4 and m68k are currently disabled. > > Adrian >