From: "H. Peter Anvin" <hpa@zytor.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
mingo@kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/tools: Fix gcc-7 warning in relocs.c
Date: Tue, 20 Dec 2016 03:10:15 -0800 [thread overview]
Message-ID: <2966d559-2cea-fd95-76d4-df34192a9b88@zytor.com> (raw)
In-Reply-To: <20161220100056.GA289@x4>
On 12/20/16 02:00, Markus Trippelsdorf wrote:
> On 2016.12.20 at 01:30 -0800, H. Peter Anvin wrote:
>> I'd strongly prefer a non-data-dependent solution, specifically adding
>> at the top of sort_relocs():
>>
>> if (!r->count)
>> return;
>>
>> However, by my reading of the C and POSIX standards, this is a gcc
>> error: qsort() should do nothing if the count is zero.
>
> No, it is invoking undefined behavior.
H
> Notice the nonnull attribute in /usr/include/stdlib.h:
>
> 739 /* Sort NMEMB elements of BASE, of SIZE bytes each,
> 740 using COMPAR to perform the comparisons. */
> 741 extern void qsort (void *__base, size_t __nmemb, size_t __size,
> 742 __compar_fn_t __compar) __nonnull ((1, 4));
>
> But feel free to revert my patch and add your solution.
Well, s/gcc/glibc/ then.
> The qsort() function shall sort an array of nel objects, the
> initial element of which is pointed to by base. The size of
> each object, in bytes, is specified by the width argument. If
> the nel argument has the value zero, the comparison function
> pointed to by compar shall not be called and no rearrangement
> shall take place.
-hpa
next prev parent reply other threads:[~2016-12-20 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 12:45 [PATCH] x86-64: " Markus Trippelsdorf
2016-12-19 10:56 ` [tip:x86/urgent] x86/tools: " tip-bot for Markus Trippelsdorf
2016-12-20 9:30 ` H. Peter Anvin
2016-12-20 10:00 ` Markus Trippelsdorf
2016-12-20 11:10 ` H. Peter Anvin [this message]
2016-12-20 11:51 ` Markus Trippelsdorf
2016-12-20 18:32 ` hpa
2016-12-20 19:31 ` Markus Trippelsdorf
2016-12-20 20:44 ` H. Peter Anvin
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=2966d559-2cea-fd95-76d4-df34192a9b88@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®