public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GLIBC patches <libc-alpha@sourceware.org>
Subject: Re: Upstreaming OpenRISC with GCC mainline
Date: Fri, 29 Oct 2021 06:17:17 +0900	[thread overview]
Message-ID: <YXsTXd7rYNsHzKH9@antec> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110281714090.1736839@digraph.polyomino.org.uk>

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 
> <https://sourceware.org/pipermail/libc-alpha/2021-October/132348.html>.

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

    malloc.c: In function ‘_int_malloc’:
    malloc.c:4226:53: error: ‘nb’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
     4226 |                   set_head (victim, nb | PREV_INUSE |
	  |                                                     ^
    malloc.c:3657:19: note: ‘nb’ was declared here
     3657 |   INTERNAL_SIZE_T nb;               /* normalized request size */
	  |                   ^~

FAIL: compilers-or1k-linux-gnu-soft glibc or1k-linux-gnu-soft build

    malloc.c: In function ‘_int_malloc’:
    malloc.c:4226:53: error: ‘nb’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
     4226 |                   set_head (victim, nb | PREV_INUSE |
	  |                                                     ^
    malloc.c:3657:19: note: ‘nb’ was declared here
     3657 |   INTERNAL_SIZE_T nb;               /* normalized request size */
	  |                   ^~

GCC: mainline   (2021-10-29 308531d148a)
GLIBC: mainline (2021-10-19 46baeb61e1)

Ill try to update GLIBC.

-Stafford

  reply	other threads:[~2021-10-28 21:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 20:49 Stafford Horne
2021-10-27 22:13 ` Joseph Myers
2021-10-27 23:19   ` Stafford Horne
2021-10-28 17:15     ` Joseph Myers
2021-10-28 21:17       ` Stafford Horne [this message]
2021-10-28 21:45         ` Joseph Myers
2021-10-28 22:18           ` Stafford Horne
2021-10-29  9:05             ` Stafford Horne
2021-10-29 14:43               ` Joseph Myers
2021-10-29 15:08                 ` Stafford Horne
2021-10-30  8:56                   ` Stafford Horne
2021-11-01 20:47                     ` Joseph Myers
2021-11-02  4:18                       ` Stafford Horne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YXsTXd7rYNsHzKH9@antec \
    --to=shorne@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).