public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/31210] [gdb, symtab] Deprecate stabs Date: Wed, 10 Jan 2024 18:22:20 +0000 [thread overview] Message-ID: <bug-31210-4717-DzfWfqPT9R@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31210-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31210 --- Comment #4 from Tom Tromey <tromey at sourceware dot org> --- See this thread though: https://inbox.sourceware.org/gdb-patches/20230119174156.654402-1-tom@tromey.com/ At least Eli was opposed IIRC. I found out today that with GCC 12 I can't even run gdb tests with stabs: murgatroyd. runtest --target_board=stabs gdb.base/whatis-ptype-typedefs.exp [...] gdb compile failed, gcc: warning: switch '-gstabs+' is no longer supported gdb compile failed, g++: warning: switch '-gstabs+' is no longer supported === gdb Summary === # of untested testcases 2 We'd need some kind of gcc wrapper. And in the future we will have to build an old compiler or something to test. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-10 18:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-04 12:27 [Bug symtab/31210] New: " vries at gcc dot gnu.org 2024-01-04 12:34 ` [Bug symtab/31210] " vries at gcc dot gnu.org 2024-01-05 10:23 ` ssbssa at sourceware dot org 2024-01-08 12:08 ` vries at gcc dot gnu.org 2024-01-08 23:22 ` tromey at sourceware dot org 2024-01-09 10:17 ` vries at gcc dot gnu.org 2024-01-10 18:22 ` tromey at sourceware dot org [this message] 2024-01-10 18:23 ` tromey at sourceware dot 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-31210-4717-DzfWfqPT9R@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).