public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] add attribute nonstring
Date: Mon, 27 Nov 2017 16:04:00 -0000	[thread overview]
Message-ID: <18efaf31-b386-3aa7-480f-640d292a2957@gmail.com> (raw)
In-Reply-To: <30e8d254-6dd0-4d0a-bdee-3af212c02a49@gotplt.org>

On 11/27/2017 04:05 AM, Siddhesh Poyarekar wrote:
> On Friday 10 November 2017 11:01 PM, Martin Sebor wrote:
>> diff --git a/sysdeps/gnu/bits/utmp.h b/sysdeps/gnu/bits/utmp.h
>> index 2ee11cb..d4885f3 100644
>> --- a/sysdeps/gnu/bits/utmp.h
>> +++ b/sysdeps/gnu/bits/utmp.h
>> @@ -59,9 +59,13 @@ struct utmp
>>  {
>>    short int ut_type;		/* Type of login.  */
>>    pid_t ut_pid;			/* Process ID of login process.  */
>> +  __NONSTRING
>>    char ut_line[UT_LINESIZE];	/* Devicename.  */
>> +  __NONSTRING
>>    char ut_id[4];		/* Inittab ID.  */
>> +  __NONSTRING
>>    char ut_user[UT_NAMESIZE];	/* Username.  */
>> +  __NONSTRING
>>    char ut_host[UT_HOSTSIZE];	/* Hostname for remote login.  */
>>    struct exit_status ut_exit;	/* Exit status of a process marked
>>  				   as DEAD_PROCESS.  */
>
> This breaks builds with the latest gcc since your commit to warn on
> non-string arguments to strlen:

I didn't see any warnings in my x86_64-linux build but there could
be others on targets I don't test.  The only problem I do know of
(bug 22447) was fixed last Wednesday.

It would be helpful if you could share some details about the code
that triggers the warning, what target, etc.

Martin

  reply	other threads:[~2017-11-27 16:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 17:31 Martin Sebor
2017-11-10 17:54 ` Joseph Myers
2017-11-10 23:11   ` Martin Sebor
2017-11-10 23:46     ` Joseph Myers
2017-11-14 17:58       ` Joseph Myers
2017-11-15 22:09     ` Steve Ellcey
2017-11-15 23:05       ` Martin Sebor
2017-11-15 23:14         ` Joseph Myers
2017-11-21  5:27           ` Paul Eggert
2017-11-21 13:38             ` Joseph Myers
2017-11-12  9:06 ` Paul Eggert
2017-11-12 17:33   ` Martin Sebor
2017-11-12 20:39     ` Paul Eggert
2017-11-12 23:49       ` Martin Sebor
2017-11-13 17:35         ` Steve Ellcey
2017-11-14 16:37           ` Joseph Myers
2017-11-14 16:50           ` Florian Weimer
2017-11-14 17:06             ` Joseph Myers
2017-11-14 17:55               ` Andreas Schwab
2017-11-14 18:21                 ` Florian Weimer
2017-11-14 18:27                   ` Joseph Myers
2017-11-14 18:29                     ` Florian Weimer
2017-11-14 23:22                       ` Steve Ellcey
2017-11-15 10:48                         ` Florian Weimer
2017-11-15 17:58                           ` glibc failures on aarch64: (Was Re: [PATCH] add attribute nonstring) Steve Ellcey
2017-11-16  0:37                             ` Adhemerval Zanella
2017-11-17 12:49                             ` Szabolcs Nagy
2017-11-17 12:57                               ` Florian Weimer
2017-11-13  0:50   ` [PATCH] add attribute nonstring Joseph Myers
2017-11-27 11:05 ` Siddhesh Poyarekar
2017-11-27 16:04   ` Martin Sebor [this message]
2017-11-27 16:24     ` Siddhesh Poyarekar
2017-11-27 16:26       ` Siddhesh Poyarekar

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=18efaf31-b386-3aa7-480f-640d292a2957@gmail.com \
    --to=msebor@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).