This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/82542] New: -fdump-lang-raw (formerly -fdump-translation-unit) no longer available for C
- From: "b.r.longbons at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 13 Oct 2017 11:07:40 +0000
- Subject: [Bug c/82542] New: -fdump-lang-raw (formerly -fdump-translation-unit) no longer available for C
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
Bug ID: 82542
Summary: -fdump-lang-raw (formerly -fdump-translation-unit) no
longer available for C
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: b.r.longbons at gmail dot com
Target Milestone: ---
With the refactoring to (sensibly I guess?) make it somehow language-specific,
it got dropped from the C FE, via which probably has more users than via the
C++ FE.
There are a *lot* of people relying on this (Debian and Glibc use it for ABI
checking; I and others use it to help generate C bindings for my toy language
without having to write a C parser for no reason).
A partial workaround is to compile as C++ with an `extern "C" { }` block around
the whole thing, but there is a lot of C syntax that doesn't compile in C++ ...
not to mention certain headers that deliberately behave *differently* in C++
mode (e.g. strchr).
Also, would it hurt to keep the old option around as an alias? That's what most
options seem to do (-std=c++0x comes to mind). That just seems like gratuitous
breakage.