This is the mail archive of the
mailing list for the glibc project.
Re: [RFC] Avoid spurious isolate-erroneous-paths failures
- From: Jeff Law <law at redhat dot com>
- To: OndÅej BÃlka <neleai at seznam dot cz>, libc-alpha at sourceware dot org
- Date: Mon, 18 Nov 2013 09:08:15 -0700
- Subject: Re: [RFC] Avoid spurious isolate-erroneous-paths failures
- Authentication-results: sourceware.org; auth=none
- References: <20131118153902 dot GA3437 at domone dot podge>
On 11/18/13 08:39, OndÅej BÃlka wrote:
a gcc isolate-erroneous-paths switch causes trapping of
memset (NULL, 0, 0), see
This could give a isolate-erroneous-paths bad reputation as it will
cause more spurious failures than real problems.
One way how to fix this would be drop nonnull attribute from mem* and
strn* function as patch below does.
I would recommend against this.
A better fallback is to leave glibc as-is and not optimize these cases
in GCC by default and improve GCC to issue warnings for this stuff.
That allows for a transition period where people can find the errors in
their code. That can't happen if glibc remove the non-null attributes.