From: Junio C Hamano <gitster@pobox.com>
To: Immolo <immoloism@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [Bug Report] Git fails to compile with fortify-headers and LTO - error: inlining failed in call to 'always_inline' 'fwrite': function body can be overwritten at link time
Date: Tue, 18 Jul 2023 16:13:02 -0700 [thread overview]
Message-ID: <xmqqcz0oerup.fsf@gitster.g> (raw)
In-Reply-To: <CAHfWF5n5kk1bYdU4qKTF3n_Ad9BGjwbbmm+0ZQEX=1NZzRiWXA@mail.gmail.com> (Immolo's message of "Wed, 19 Jul 2023 00:06:50 +0100")
Immolo <immoloism@googlemail.com> writes:
> /usr/include/fortify/stdio.h: In function 'verify_cache':
> /usr/include/fortify/stdio.h:59:28: error: inlining failed in call to
> 'always_inline' 'fwrite': function body can be overwritten at link
> time
> 59 | _FORTIFY_FN(fwrite) size_t fwrite(const void *__d, size_t __n,
> size_t __m, FILE *__f)
> | ^
> cache-tree.c:175:33: note: called from here
> 175 | fprintf(stderr, "...\n");
> | ^
It looks like a plain vanilla invocation of fprintf(), unlike from
any random application, a user of the standard C runtime library .
Is this a bug to be reported here, or would it be more valuable and
useful if reported to GCC or Fortify folks, I wonder?
next prev parent reply other threads:[~2023-07-18 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 23:06 [Bug Report] Git fails to compile with fortify-headers and LTO - error: inlining failed in call to 'always_inline' 'fwrite': function body can be overwritten at link time Immolo
2023-07-18 23:13 ` Junio C Hamano [this message]
2023-07-18 23:18 ` Immolo
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=xmqqcz0oerup.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=immoloism@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.