git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Immolo <immoloism@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
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: Wed, 19 Jul 2023 00:18:36 +0100	[thread overview]
Message-ID: <CAHfWF5mjquES-nocQaK+CAEsqWgdy-_OYdGtN82heYs0eJP3eQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqcz0oerup.fsf@gitster.g>

I've reported to the folks over at fortify-headers already and they
came to the same conclusion (minus GCC), it's an odd one that's for
sure.

Immolo

On Wed, 19 Jul 2023 at 00:13, Junio C Hamano <gitster@pobox.com> wrote:
>
> 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?
>

      reply	other threads:[~2023-07-18 23:19 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
2023-07-18 23:18   ` Immolo [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHfWF5mjquES-nocQaK+CAEsqWgdy-_OYdGtN82heYs0eJP3eQ@mail.gmail.com \
    --to=immoloism@googlemail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).