public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pdimov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102350] New: __builtin_source_location not available in earlier language modes Date: Wed, 15 Sep 2021 15:09:43 +0000 [thread overview] Message-ID: <bug-102350-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102350 Bug ID: 102350 Summary: __builtin_source_location not available in earlier language modes Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pdimov at gmail dot com Target Milestone: --- Currently, `__builtin_source_location` requires (a) `<source_location>` to be included and (b) -std=c++20. Are there good reasons for these restrictions? The builtin would still be extremely valuable in earlier language modes. Libraries that still support 03/11/14/17 (Boost.System, for instance) could transparently supply source locations by using a default `void const* loc = __builtin_source_location()` argument.
next reply other threads:[~2021-09-15 15:09 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 15:09 pdimov at gmail dot com [this message] 2021-09-15 16:39 ` [Bug c++/102350] " jakub at gcc dot gnu.org 2021-09-15 17:37 ` pdimov at gmail dot com 2021-09-15 19:49 ` redi at gcc dot gnu.org 2021-09-15 21:12 ` pdimov at gmail dot com 2021-09-16 9:38 ` redi at gcc dot gnu.org 2021-09-16 9:50 ` jakub at gcc dot gnu.org 2021-09-16 10:13 ` pdimov at gmail dot com 2021-09-16 10:15 ` pdimov at gmail dot com 2021-09-16 10:19 ` jakub at gcc dot gnu.org 2021-09-16 10:24 ` pdimov at gmail dot com 2021-09-16 10:41 ` jakub at gcc dot gnu.org 2021-09-16 10:50 ` redi at gcc dot gnu.org 2021-09-16 10:53 ` redi at gcc dot gnu.org 2021-09-16 10:53 ` jakub at gcc dot gnu.org 2021-09-16 10:59 ` pdimov at gmail dot com 2021-09-16 11:02 ` pdimov at gmail dot com 2021-09-16 11:11 ` jakub at gcc dot gnu.org 2021-09-16 11:34 ` pdimov at gmail dot com 2021-09-16 11:54 ` redi 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-102350-4@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: linkBe 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).