public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109506] [10/11/12/13 regression] -fchecking=2 causes some template constructor not be instantiated when used with NSDMI
Date: Thu, 13 Apr 2023 22:01:17 +0000 [thread overview]
Message-ID: <bug-109506-4-h5ugf7N0GH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109506-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109506
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[13 regression] 'error: |[10/11/12/13 regression]
|inlining failed in call to |-fchecking=2 causes some
|‘always_inline’ |template constructor not be
|‘foo<T>::foo() [with T = |instantiated when used with
|void]’: function body not |NSDMI
|available' |
Target Milestone|13.0 |10.5
Known to fail| |12.2.0
Known to work|12.2.0 |
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>On our box, I bisected this to r251422. Surely that isn't the real cause of the problem.
it is in the end as oh yes adding -fchecking=2 causes the failure in released
versions.
next prev parent reply other threads:[~2023-04-13 22:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 21:31 [Bug c++/109506] New: [13 regression] 'error: inlining failed in call to ‘always_inline’ ‘foo<T>::foo() [with T = void]’: function body not available' sjames at gcc dot gnu.org
2023-04-13 21:38 ` [Bug c++/109506] " pinskia at gcc dot gnu.org
2023-04-13 21:41 ` pinskia at gcc dot gnu.org
2023-04-13 21:50 ` mpolacek at gcc dot gnu.org
2023-04-13 21:56 ` pinskia at gcc dot gnu.org
2023-04-13 21:57 ` pinskia at gcc dot gnu.org
2023-04-13 22:01 ` pinskia at gcc dot gnu.org [this message]
2023-04-13 22:18 ` [Bug c++/109506] [10/11/12/13 regression] -fchecking=2 causes some template constructor not be instantiated when used with NSDMI pinskia at gcc dot gnu.org
2023-04-13 22:19 ` pinskia at gcc dot gnu.org
2023-04-15 1:15 ` sjames at gcc dot gnu.org
2023-04-17 17:33 ` [Bug c++/109506] [10/11/12/13/14 " ppalka at gcc dot gnu.org
2023-04-27 15:20 ` ppalka at gcc dot gnu.org
2023-05-02 12:49 ` cvs-commit at gcc dot gnu.org
2023-05-05 15:22 ` [Bug c++/109506] [10/11/12/13 " cvs-commit at gcc dot gnu.org
2023-07-07 10:45 ` [Bug c++/109506] [11/12 " rguenth at gcc dot gnu.org
2023-08-11 19:19 ` jason 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-109506-4-h5ugf7N0GH@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).