public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lsix at lancelotsix dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31420] Use std::filesystem::remove_all in compile.c Date: Thu, 04 Apr 2024 07:37:42 +0000 [thread overview] Message-ID: <bug-31420-4717-TuhJDfcRKC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31420-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31420 Lancelot SIX <lsix at lancelotsix dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lsix at lancelotsix dot com --- Comment #4 from Lancelot SIX <lsix at lancelotsix dot com> --- I had a look a t various compiler versions. - gcc-7.5 does not have std::filesystem support available, so if we want to keep supporting this compiler, we can't move to remove_all. - gcc-8 has std::filesystem, but using it require using "-lstdc++fs". Supporting this compiler would require an extra configure step to check if this flag is required. - starting gcc-9, std::filesytem is available without extra compiler flags. For now, I think we will try to maintain gcc-7.5 compatibility as it is still used. This will need to be revisited at some point. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-04 7:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-27 17:02 [Bug gdb/31420] New: " tromey at sourceware dot org 2024-02-27 17:02 ` [Bug gdb/31420] " tromey at sourceware dot org 2024-02-27 17:25 ` tromey at sourceware dot org 2024-04-03 12:54 ` cvs-commit at gcc dot gnu.org 2024-04-03 15:31 ` cvs-commit at gcc dot gnu.org 2024-04-04 7:37 ` lsix at lancelotsix dot com [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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31420-4717-TuhJDfcRKC@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).