public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: sellcey@cavium.com
Cc: DJ Delorie <dj@redhat.com>, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [Patch] Fix nss/nss_test1.c compile with latest GCC
Date: Fri, 21 Jul 2017 23:02:00 -0000	[thread overview]
Message-ID: <CAMe9rOrRtvGg-ymAvj3Zo9iwhsr_nNn_qU5AfwLoBYDUCRav7Q@mail.gmail.com> (raw)
In-Reply-To: <1500656090.28549.42.camel@cavium.com>

On Fri, Jul 21, 2017 at 9:54 AM, Steve Ellcey <sellcey@cavium.com> wrote:
> On Wed, 2017-07-19 at 19:13 -0400, DJ Delorie wrote:
>> Steve Ellcey <sellcey@cavium.com> writes:
>> >
>> > I think this is due to new error checking added to GCC and in this
>> > case I think that GCC is correct in its error.  We should
>> > be using the default_pwd_data in this expression and not pwd_data.
>> Correct, although no existing tests actually use that data, so the
>> bug
>> (and the fix) do not affect test results.
>>
>> >
>> > This patch fixes the proglem, OK for checkin?
>> I was going to check in the same patch... but my rawhide gcc didn't
>> give
>> a warning so I haddn't yet confirmed it.
>>
>> So LGTM :-)
>>
>> Thanks!
>
> Since there haven't seen any objections to this I am going to go ahead
> and check it in.
>

On Fedora 26, this caused:

[hjl@gnu-tools-1 build-x86_64-linux]$ nss/tst-nss-test5
[1] passwd entry 30.name30 had uid 300
[1] passwd entry 30.name30 had pw_name "name300" (expected "name30")
    passwd 300.name300 (*) : 100, *, *, *

    passwd 30.name30 (*) : 100, *, *, *

[2] passwd pw_name for 200.name200 was (null)
    passwd 200.(null) (*) : 100, *, *, *

    passwd 200.name200 (*) : 100, *, *, *

[3] passwd pw_name for 60.(null) was name60
    passwd 60.name60 (*) : 100, *, *, *

    passwd 60.(null) (*) : 100, *, *, *

[4] passwd entry 20000.name20000 had gid 200 (expected 100)
    passwd 20000.name20000 (*) : 200, *, *, *

    passwd 20000.name20000 (*) : 100, *, *, *

[5] passwd entry 2.name2 had gid 2 (expected 100)
[5] passwd entry 2.name2 had pw_passwd "x" (expected "*")
[5] passwd entry 2.name2 had pw_gecos "y" (expected "*")
[5] passwd entry 2.name2 had pw_dir "z" (expected "*")
    passwd 2.name2 (x) : 2, y, z, *

    passwd 2.name2 (*) : 100, *, *, *

FAIL: [?] passwd entry 30.name30 unexpected
FAIL: Found 10 errors, expected 9
[hjl@gnu-tools-1 build-x86_64-linux]$



-- 
H.J.

  reply	other threads:[~2017-07-21 23:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 21:17 Steve Ellcey
2017-07-19 23:13 ` DJ Delorie
2017-07-21 16:55   ` Steve Ellcey
2017-07-21 23:02     ` H.J. Lu [this message]
2017-07-21 23:17       ` H.J. Lu
2017-07-21 23:23         ` DJ Delorie
2017-07-21 23:35           ` H.J. Lu
2017-07-21 23:51             ` DJ Delorie
2017-07-21 23:55               ` Steve Ellcey

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=CAMe9rOrRtvGg-ymAvj3Zo9iwhsr_nNn_qU5AfwLoBYDUCRav7Q@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sellcey@cavium.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).