From: "H.J. Lu" <hjl.tools@gmail.com>
To: Stefan Liebler <stli@linux.vnet.ibm.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Dynamic growable arrays for internal use
Date: Tue, 06 Jun 2017 15:46:00 -0000 [thread overview]
Message-ID: <CAMe9rOopA0YfCt-aRBrZNS4t38XmuLzr0eEe8UM2Xu3Rv_r2=w@mail.gmail.com> (raw)
In-Reply-To: <37f01ed4-1443-8585-42cb-1b7759416ee7@linux.vnet.ibm.com>
On Tue, Jun 6, 2017 at 8:30 AM, Stefan Liebler <stli@linux.vnet.ibm.com> wrote:
> Hi Florian,
>
> I get the following warning / werror with gcc 4.8.5 on s390x:
> gcc tst-dynarray.c -O3 -c ... -o <build>/malloc/tst-dynarray.o
> In file included from tst-dynarray.c:50:0:
> tst-dynarray.c: In function ‘do_test’:
> ../support/check.h:51:8: error: ‘result.length’ may be used uninitialized in
> this function [-Werror=maybe-uninitialized]
> if (expr) \
> ^
> tst-dynarray.c:377:23: note: ‘result.length’ was declared here
> struct long_array result;
> ^
> In file included from tst-dynarray.c:50:0:
> ../support/check.h:51:8: error: ‘result.array’ may be used uninitialized in
> this function [-Werror=maybe-uninitialized]
> if (expr) \
> ^
> tst-dynarray.c:377:23: note: ‘result.array’ was declared here
> struct long_array result;
> ^
> cc1: all warnings being treated as errors
>
>
> Have you seen those warnings on other architectures, too?
>
I also see:
../Rules:198: target
'/export/build/gnu/glibc-test/build-x86_64-linux/malloc/tst-dynarray'
given more than once in the same rule
../Rules:198: target
'/export/build/gnu/glibc-test/build-x86_64-linux/malloc/tst-dynarray-fail'
given more than once in the same rule
--
H.J.
next prev parent reply other threads:[~2017-06-06 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 15:46 Florian Weimer
2017-04-24 14:06 ` Joseph Myers
2017-05-05 11:48 ` Florian Weimer
2017-05-05 15:13 ` Paul Eggert
2017-05-05 15:23 ` Florian Weimer
2017-05-05 22:31 ` Paul Eggert
2017-05-20 2:01 ` Carlos O'Donell
2017-05-21 0:43 ` Paul Eggert
2017-06-01 16:13 ` Carlos O'Donell
2017-06-01 17:09 ` Jeff Law
2017-06-01 20:21 ` Florian Weimer
2017-06-01 21:13 ` Adhemerval Zanella
2017-06-01 18:08 ` Paul Eggert
2017-05-30 12:48 ` Florian Weimer
2017-06-02 7:37 ` Carlos O'Donell
2017-06-02 10:04 ` Florian Weimer
2017-06-06 15:30 ` Stefan Liebler
2017-06-06 15:46 ` H.J. Lu [this message]
2017-06-07 9:54 ` Florian Weimer
2017-06-07 9:41 ` Florian Weimer
2017-06-07 14:41 ` Stefan Liebler
2017-06-07 18:56 ` Florian Weimer
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='CAMe9rOopA0YfCt-aRBrZNS4t38XmuLzr0eEe8UM2Xu3Rv_r2=w@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.vnet.ibm.com \
/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).