public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105234] inlining failed in call to 'always_inline' 'memset': target specific option mismatch
Date: Tue, 12 Apr 2022 02:58:16 +0000	[thread overview]
Message-ID: <bug-105234-4-esub5YnVQd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105234-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234

--- Comment #3 from Khem Raj <raj.khem at gmail dot com> ---
Second sample works when I do not use _FORTIFY_SOURCES=2, so perhaps gcc-12
needs to adjust some glibc headers ?

  parent reply	other threads:[~2022-04-12  2:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  2:28 [Bug c++/105234] New: nlining failed in call to 'always_inline' 'fmt::v8::basic_format_string<Char, Args>::basic_format_string(const S&) raj.khem at gmail dot com
2022-04-12  2:49 ` [Bug c++/105234] inlining " raj.khem at gmail dot com
2022-04-12  2:49 ` raj.khem at gmail dot com
2022-04-12  2:58 ` raj.khem at gmail dot com [this message]
2022-04-12  8:51 ` [Bug target/105234] inlining failed in call to 'always_inline' 'memset': target specific option mismatch marxin at gcc dot gnu.org
2022-04-12  8:51 ` marxin at gcc dot gnu.org
2022-04-12  9:45 ` [Bug target/105234] [12 Regression] inlining failed in call to 'always_inline' 'memset': target specific option mismatch since r12-5920-g01ad8c54fdca1d marxin at gcc dot gnu.org
2022-04-12 10:32 ` jakub at gcc dot gnu.org
2022-04-12 10:33 ` jakub at gcc dot gnu.org
2022-04-12 10:45 ` jakub at gcc dot gnu.org
2022-04-12 10:49 ` redi at gcc dot gnu.org
2022-04-12 11:00 ` marxin at gcc dot gnu.org
2022-04-12 11:03 ` jakub at gcc dot gnu.org
2022-04-12 11:09 ` jakub at gcc dot gnu.org
2022-04-12 11:16 ` marxin at gcc dot gnu.org
2022-04-13  1:50 ` linkw at gcc dot gnu.org
2022-04-13  8:14 ` cvs-commit at gcc dot gnu.org
2022-04-13  8:36 ` jakub at gcc dot gnu.org

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=bug-105234-4-esub5YnVQd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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. 
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).