diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-03-11 11:07:15 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-03-11 11:07:15 +0100 |
| commit | 3f717f9565c5c40bcaa1e0b5419fe5bf65ad7f1c (patch) | |
| tree | fda2c7b169b1e33283af7b97796570321b75d1cb /gcc/c | |
| parent | 8e1efc3c864928e3447880caceddb6fa0d45bc46 (diff) | |
| download | gcc-3f717f9565c5c40bcaa1e0b5419fe5bf65ad7f1c.zip gcc-3f717f9565c5c40bcaa1e0b5419fe5bf65ad7f1c.tar.gz gcc-3f717f9565c5c40bcaa1e0b5419fe5bf65ad7f1c.tar.bz2 | |
cobol: Use *.cc suffix for bison/flex generated C++ files
In GCC 12 we've switched to using *.cc suffixes for C++ sources in GCC
sources, including generated files, instead of using *.c suffixes and
compiling them as C++ anyway (that was the case since we've switched
GCC to C++ in GCC 4.8).
I've noticed gcc/cobol has 3 generated files still with c extension
despite clearly having C++ code in it and being compiled as C++.
2025-03-11 Jakub Jelinek <jakub@redhat.com>
* Make-lang.in (cobol/parse.c, cobol/cdf.c, cobol/scan.c): Remove.
(cobol/parse.cc, cobol/cdf.cc, cobol/scan.cc): New goals.
(cobol/cdf.o): Depend on cobol/cdf.cc rather than cobol/cdf.c.
(cobol/parse.o): Depend on cobol/parse.cc rather than cobol/parse.c.
(cobol/scan.o): Depend on cobol/scan.cc rather than cobol/scan.c,
on cobol/cdf.cc rather than cobol/cdf.c and on cobol/parse.cc rather
than cobol/parse.c.
(cobol.srcextra): Depend on cobol/parse.cc cobol/cdf.cc cobol/scan.cc
rather than cobol/parse.c cobol/cdf.c cobol/scan.c.
Diffstat (limited to 'gcc/c')
0 files changed, 0 insertions, 0 deletions