From: Gerald Pfeifer <gerald@pfeifer.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/2] libsanitizer: Merge with upstream commit fdf4c035225d
Date: Sun, 10 Oct 2021 00:28:14 +0200 (CEST) [thread overview]
Message-ID: <5a20d58-d9ec-aebf-a24-edf4f8a877ca@pfeifer.com> (raw)
In-Reply-To: <CAMe9rOq4YPdA+Pz9Heiswu7Cd38JCfR1fG5fwRtV2JZW=7iigw@mail.gmail.com>
On Thu, 7 Oct 2021, H.J. Lu wrote:
>> Thus breaking bootstrap on FreeBSD:
>>
>> GCC-HEAD/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp:370:36: error: 'MD5_CTX' was not declared in this scope
> 370 | const unsigned MD5_CTX_sz = sizeof(MD5_CTX);
>> | ^~~~~~~
>> GCC-HEAD/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp:371:36: error:
>> 'MD5_DIGEST_STRING_LENGTH' was not declared in this scope
> compiler-rt sync brought in
>
> commit 18a7ebda99044473fdbce6376993714ff54e6690
> Author: David Carlier <devnexen@gmail.com>
> Date: Wed Oct 6 06:01:50 2021 +0100
>
> [Sanitizers] intercept md5 and sha* apis on FreeBSD.
>
> Reviewed By: vitalybuka
>
> Differential Revision: https://reviews.llvm.org/D110989
>
> diff --git a/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp
> b/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp
> index bfe3eea464d..64535805e40 100644
> --- a/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp
> +++ b/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp
> @@ -69,6 +69,11 @@
> #include <semaphore.h>
> #include <signal.h>
> #include <stddef.h>
> +#include <md5.h>
Yep, and here is the problem: In the case of Clang this uses FreeBSD's
<md5.h>.
In the case of GCC apparently this uses our own, bare-bone md5.h -
include/md5.h.
Boom. Regression. Bootstrap failure on every platfor and version of
FreeBSD. (FreeBSD 11.x is also broken by this patch, in a different
way, alas went end of life a week ago.)
I now filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102675 and
sadly don't have an idea how to tackle this.
Gerald
prev parent reply other threads:[~2021-10-09 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 20:07 H.J. Lu
2021-10-06 20:07 ` [PATCH 1/2] libsanitizer: Merge with upstream H.J. Lu
2021-10-06 20:07 ` [PATCH 2/2] libsanitizer: Apply local patches H.J. Lu
2021-10-07 21:40 ` [PATCH 0/2] libsanitizer: Merge with upstream commit fdf4c035225d Gerald Pfeifer
2021-10-07 21:56 ` H.J. Lu
2021-10-09 22:28 ` Gerald Pfeifer [this message]
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=5a20d58-d9ec-aebf-a24-edf4f8a877ca@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
/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).