From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by sourceware.org (Postfix) with ESMTPS id 125AF3858C39 for ; Fri, 29 Oct 2021 09:05:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 125AF3858C39 Received: by mail-pg1-x52f.google.com with SMTP id j9so1167688pgh.1 for ; Fri, 29 Oct 2021 02:05:12 -0700 (PDT) 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:content-transfer-encoding :in-reply-to; bh=neLtAYUoT9soElGvqZmAlbmoz6BaP0/buH2aBZJq5ro=; b=W752mUanm8w3Kjz/HDdPbDeBERmbqd3JJn77vEF8Debs21z3EFAnzVfXvE1eppbUx8 +1RvYTxQZ1yihpt7xdb2MUXADnxdO6auWgzTsWfhat9WFyhPS8ccw8LpSM6x5++Ne8dF TJvSvJGCpIYbCACPpq0/cJhAimD+khHfMrBE6Ts3R2ohzPHynuLs3rhka6opA9+ex8q9 42D95ktrGDfqLyU1AfRePJuC/lGffWRzW+3tK3PO1eAHe+tTCTWTVnOHn6rnu16LSdd3 zLZYEUvBjMD7gmiKcXJC+RGELaEqcv0Mvxv8Sv39UFEiDAMnLn4krWjpk4goMW1WFrJc d3tQ== X-Gm-Message-State: AOAM530hzL5wBHAlYr0vZIxRoLu1P4pZOlgcHV8Va9OT799dpJ8fs7XS p6fRhPJVGcne61lqZphJAPXjF9Wt0zU= X-Google-Smtp-Source: ABdhPJx/BteGqETIqMadwDaoM1CkhvsF6ptfIWFqks9EnenHnskK/sK1bNre3gON/j6XwPC94GylrQ== X-Received: by 2002:a05:6a00:2a9:b0:47b:db92:76a1 with SMTP id q9-20020a056a0002a900b0047bdb9276a1mr9390434pfs.37.1635498311139; Fri, 29 Oct 2021 02:05:11 -0700 (PDT) Received: from localhost ([2409:10:24a0:4700:e8ad:216a:2a9d:6d0c]) by smtp.gmail.com with ESMTPSA id d15sm6452624pfv.22.2021.10.29.02.05.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 Oct 2021 02:05:10 -0700 (PDT) Date: Fri, 29 Oct 2021 18:05:08 +0900 From: Stafford Horne To: Joseph Myers Cc: GLIBC patches Subject: Re: Upstreaming OpenRISC with GCC mainline Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-4.3 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: Fri, 29 Oct 2021 09:05:14 -0000 On Fri, Oct 29, 2021 at 07:18:45AM +0900, Stafford Horne wrote: > On Thu, Oct 28, 2021 at 09:45:51PM +0000, Joseph Myers wrote: > > On Fri, 29 Oct 2021, Stafford Horne via Libc-alpha wrote: > > > > > On Thu, Oct 28, 2021 at 05:15:00PM +0000, Joseph Myers wrote: > > > > On Thu, 28 Oct 2021, Stafford Horne via Libc-alpha wrote: > > > > > > > > > I was seeing failures there and thought the warnings I was seeing were > > > > > affecting all architectures. But now I see the builds are mostly clean. > > > > > So it's something I'll have to track down. > > > > > > > > The only issue I know of at present with GCC mainline is the testsuite > > > > build failures for 32-bit platforms that are addressed by my patch > > > > . > > > > > > Thanks, yes I saw that patch. > > > > > > I am trying to compare builds of multiple architectures. I do see similar > > > errors on riscv32. I am continuing to try looking at other architectures, but > > > just wanted to note this: > > > > > > FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 glibc riscv32-linux-gnu-rv32imac-ilp32 build > > > > Since I don't see this, do you have environment variables set (e.g. > > CFLAGS) that might perturb the build? You're not meant to have such > > variables set when running build-many-glibcs.py, and can definitely expect > > additional warnings with -O1 or -O3, for example. (We *should* fix things > > to build cleanly with -O1 and -O3 and -Os and -Og, and even -O0, but > > that's a separate issue.) > > Thats it, I have -Og setup in my build environment. > > I must have missed where that was mentioned. > Hi Joseph, Do you store your full output results anywhere for build-many, i.e. GCC mainline glibcs 2021-10-28 16:33:56 build results - https://sourceware.org/pipermail/libc-testresults/2021q4/008777.html I am getting these failures now, and am wondering if you see them too: $ or1k-glibc-linux-gnu-gcc tst-mqueue5.c -c -std=gnu11 -fgnu89-inline -g -O -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fno-stack-protector -fno-c.... tst-mqueue5.c: In function ‘mqsend’: tst-mqueue5.c:61:7: error: ‘c’ may be used uninitialized [-Werror=maybe-uninitialized] 61 | if (mq_send (q, &c, 1, 1) != 0) | ^~~~~~~~~~~~~~~~~~~~~ In file included from ../include/mqueue.h:1, from tst-mqueue5.c:21: ../rt/mqueue.h:70:12: note: by argument 2 of type ‘const char *’ to ‘mq_send’ declared here 70 | extern int mq_send (mqd_t __mqdes, const char *__msg_ptr, size_t __msg_len, | ^~~~~~~ tst-mqueue5.c:60:8: note: ‘c’ declared here 60 | char c; | ^ -Stafford