From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) by sourceware.org (Postfix) with ESMTPS id 873763858D28 for ; Wed, 15 Dec 2021 05:37:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 873763858D28 Received: by mail-pj1-x1029.google.com with SMTP id r34-20020a17090a43a500b001b0f0837ce8so3206279pjg.2 for ; Tue, 14 Dec 2021 21:37:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=OPE16NGUehq7H+GPj7sdm2nwjOe6Q0+oH4ixzeF6Z+Y=; b=Qb3gZubph0HuSTnqyIygulxqK+EZs8mhhue2AaBmYtjHrKfuIeAZPmhTVvYrAb2c02 JTTcycFWTgFFhyX7jMc1XCNaNrlHVyTF+ZuuNcWZDY4z2iZNN7Q7eZcIogOuJn8JC99s aD8yWuW5G1H5m/IuQPLkXJ9qPQkTocdyEGA5Zih4uO6oIm5KtfRYFy/9quGxkyFnY2WO sOXiHZBcSsKbgR2GPPDtLu5BVpkARftznCZaYaOukDqPfab+NZN2Dfg69detgMZFcsAT zkZHbMun86yZAyJWiwq/saStpcqqnPZ0CPpiP5++CGVQvKFQOHq2Bs3hXSqBikMqjCo0 YYVw== X-Gm-Message-State: AOAM531SWcFumkNOgG2EsE6EoreaB/5dWc0bnHKqc8FAlB/7Iyvps9iT Vj3Fp6buvpFclDHey65RXKU= X-Google-Smtp-Source: ABdhPJzNps9gO/Cp/w0Dz96hbV+JeE7HyABREpcgsAxBOSwIvzsE+kZ0zY67RqIjdDt8VWnVeGxa5Q== X-Received: by 2002:a17:90b:1217:: with SMTP id gl23mr9906895pjb.191.1639546645443; Tue, 14 Dec 2021 21:37:25 -0800 (PST) Received: from localhost ([2409:10:24a0:4700:e8ad:216a:2a9d:6d0c]) by smtp.gmail.com with ESMTPSA id v11sm1018585pfu.184.2021.12.14.21.37.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Dec 2021 21:37:24 -0800 (PST) Date: Wed, 15 Dec 2021 14:37:23 +0900 From: Stafford Horne To: Adhemerval Zanella Cc: GLIBC patches , Openrisc Subject: Re: [PATCH v3 00/13] Glibc OpenRISC port Message-ID: References: <20211210233456.4146479-1-shorne@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2021 05:37:28 -0000 On Tue, Dec 14, 2021 at 05:25:09PM -0300, Adhemerval Zanella wrote: > > > On 10/12/2021 20:34, Stafford Horne via Libc-alpha wrote: > > This is the OpenRISC port for glibc that I have been working on. > > > > Changes since v2: > > - Fixed suggestions from Joseph Myers: > > - Fix comment style, and description on top of each file > > - Make sure macros have parentheses when needed, > > - Bump required kernel down to 5.4.0 and document > > - Regenerate arch-syscall.h > > - Fixed suggestions from Adhemerval: > > - Remove kernel_stat.h > > - Just set MMAP2_PAGE_UNIT to 8K > > - Remove ioctl.c and syscall.c files > > - Update TCB alignment to 32 bytes > > > > Changes since v1: > > - Update api's as suggested by Florian > > - Remove hard float support > > - Updates to get all tests passing > > - Split patch into managable bits similar to recent ARC port > > > > Documentation: > > > > Architecture / ABI docs: > > https://raw.githubusercontent.com/openrisc/doc/master/openrisc-arch-1.3-rev1.pdf > > > > Test Results: > > > > build-many-glibcs.py: > > > > PASS with mainline ang gcc-11. > > > > Full test suite: > > > > The full suite is running using the gcc-11 branch of GCC, mainline shows > > issues with math soft-fp. > > > > Note, there are a few more failures compared to before, this is due to me > > running with a timeout of 30 vs usual 300. It allows the tests to complete > > faster, but I get a few more timeouts. There were 15 timeouts which I > > confirm do work if I increase the timeoutfactor. The 2 real failures marked > > with * below. > > > > # test start: 2021-12-08T19:59:00+09:00 > > > > # failures > > FAIL:*elf/tst-bz15311 > > This seems to be a real issue, the output shows the new sorting algorithm seems > not be enabled (the output shows the destructor order for dynamic_sort=1). We > need to figure out what is happening here. > > > FAIL: locale/tst-localedef-path-norm > > FAIL: malloc/tst-dynarray-fail > > FAIL: malloc/tst-dynarray-fail-mem > > FAIL: nptl/tst-mutex10 > > FAIL: nss/tst-nss-files-hosts-getent > > FAIL: nss/tst-nss-files-hosts-multi > > FAIL: posix/tst-regcomp-truncated > > FAIL: stdio-common/tst-vfprintf-width-prec > > FAIL: stdio-common/tst-vfprintf-width-prec-alloc > > FAIL: stdio-common/tst-vfprintf-width-prec-mem > > FAIL: string/test-memcpy > > FAIL: string/test-memcpy-large > > FAIL: string/test-mempcpy > > FAIL: string/tst-cmp > > FAIL: support/tst-support_blob_repeat > > FAIL:*timezone/tst-tzset > > It seems the testing file system does not support sparse files or at least > has some limits of the file size and support_descriptor_supports_holes is > no deteting it. Let me see if I can figure out the sparse file support. If that can work then it would be good. The filesystem I am using is: tmpfs on /tmp type tmpfs (rw,relatime) > I think we should use a large write_offset and block_headroom, maybe > something larger than 32-bit offset to actually check it. Could you > check if increasing both values does make the test unsupported. I will check. -Stafford