git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 18, 2023, 23:13 UTC
Message-ID
<xmqqcz0oerup.fsf@gitster.g>
In-Reply-To
<CAHfWF5n5kk1bYdU4qKTF3n_Ad9BGjwbbmm+0ZQEX=1NZzRiWXA@mail.gmail.com>
Immolo <immoloism@googlemail.com> writes:
Show 10 quoted lines
> /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?

Previous: ImmoloNext: Immolo
Message 2 of 3 in “[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”
  1. ImmoloJul 18, 2023
  2. Junio C HamanoJul 18, 2023
  3. ImmoloJul 18, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.