This is the mail archive of the
mailing list for the GCC project.
Re: Patch ping
- From: DJ Delorie <dj at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: bonzini at gnu dot org, aoliva at redhat dot com, Ralf dot Wildenhues at gmx dot de, rguenther at suse dot de, gcc-patches at gcc dot gnu dot org
- Date: Thu, 10 Apr 2014 12:01:31 -0400
- Subject: Re: Patch ping
- Authentication-results: sourceware.org; auth=none
- References: <20140409130721 dot GK1817 at tucnak dot redhat dot com> <201404092229 dot s39MTmXp015920 at greed dot delorie dot com> <20140410055906 dot GP1817 at tucnak dot redhat dot com>
> But ubsan is a new feature in 4.9, and it is a bootstrap failure
> with that feature.
I will leave it up to the release manager to decide if they want this
non-regression patch applied before the branch, then.
> This is for the host libiberty only, and only when gcc is configured
> a certain way. The intent is to have libiberty that is going to be
> linked into all the build and host tools instrumented, so that we
> actually catch bugs in libiberty or bugs in host/build tools calling
> libiberty functions as much as possible, but for the lto-plugin,
> which is dlopened by the linker which we don't have a control on, we
> need host libiberty without the address sanitization because
> otherwise it would only work properly if the linker itself has been
> address sanitized.
So, if libiberty isn't built with sanitization, it would still *work*
but not be instrumented?