unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Martin Sebor via Libc-alpha <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] more out of bounds checking improvements
Date: Mon, 10 May 2021 21:50:36 +0200	[thread overview]
Message-ID: <877dk65pwz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <877dk64cmx.fsf@igel.home> (Andreas Schwab's message of "Mon, 10 May 2021 21:22:46 +0200")

* Andreas Schwab:

> On Mai 10 2021, Martin Sebor via Libc-alpha wrote:
>
>> It doesn't need to be disabled for GCC 11 but I don't know how to
>> be this selective with these version macros.  If it's okay to use
>> __GNUC__ then this works:
>>
>> index 9389f6b548..6a061e6457 100644
>> --- a/nss/makedb.c
>> +++ b/nss/makedb.c
>> @@ -792,7 +792,15 @@ write_output (int fd)
>>                           + nhashentries_total * sizeof (stridx_t)));
>>    header->allocate = file_offset;
>>
>> -  /* Help GCC 10 see iov_nelts doesn't overflow the writev argument.  */
>> +  assert (iov_nelts <= INT_MAX);
>> +
>> +#if __GNUC__ == 10
>
> You can use __GNUC_PREREQ (10, 0) && !__GNUC_PREREQ (11, 0)

That works for me too.

I've tested the previous version (partially quoted above) with GCC 11
and GCC 10, and it builds.

It's too late for me to test Andreas' proposal today, but I think it
should be safe to push it.  I can retest it tomorrow with GCC 9/10/11,
just to be sure.

Thanks,
Florian


  reply	other threads:[~2021-05-10 19:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 15:01 [PATCH] more out of bounds checking improvements Martin Sebor via Libc-alpha
2020-10-26 15:41 ` Florian Weimer via Libc-alpha
2020-12-09  0:18   ` Martin Sebor via Libc-alpha
2020-10-26 16:08 ` Joseph Myers
2020-12-09 21:46   ` Martin Sebor via Libc-alpha
2020-12-18 16:56     ` Ping: " Martin Sebor via Libc-alpha
2021-01-04 15:54       ` Ping 2: " Martin Sebor via Libc-alpha
2021-01-10 20:44         ` Ping 3: " Martin Sebor via Libc-alpha
2021-04-22 21:36           ` Ping 4: " Martin Sebor via Libc-alpha
2021-04-23 10:31     ` Florian Weimer via Libc-alpha
2021-04-23 15:06       ` Martin Sebor via Libc-alpha
2021-04-23 16:01         ` Florian Weimer via Libc-alpha
2021-05-04 19:58           ` Martin Sebor via Libc-alpha
2021-05-06 17:03             ` Martin Sebor via Libc-alpha
2021-05-06 18:15               ` Joseph Myers
2021-05-06 19:40                 ` Martin Sebor via Libc-alpha
2021-05-07  9:20               ` Andreas Schwab
2021-05-07  9:24                 ` Florian Weimer via Libc-alpha
2021-05-07 11:48                   ` Andreas Schwab
2021-05-07 19:30                 ` Tulio Magno Quites Machado Filho via Libc-alpha
2021-05-10 17:23                   ` Joseph Myers
2021-05-10  8:45               ` Florian Weimer via Libc-alpha
2021-05-10 17:14                 ` Martin Sebor via Libc-alpha
2021-05-10 17:49                   ` Florian Weimer via Libc-alpha
2021-05-10 18:37                     ` Martin Sebor via Libc-alpha
2021-05-10 19:22                       ` Andreas Schwab
2021-05-10 19:50                         ` Florian Weimer via Libc-alpha [this message]
2021-05-10 20:31                           ` Martin Sebor via Libc-alpha
2021-05-11 10:53                             ` Florian Weimer via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=877dk65pwz.fsf@oldenburg.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=schwab@linux-m68k.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).