From 87677ac7fbe12cd180e4a3c0ab4c209e08df98e8 Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Tue, 25 Sep 2018 09:11:05 +0200 Subject: Remove Pascal-related entries in code and comments. 2018-09-25 Martin Liska * config/powerpcspe/powerpcspe.c (rs6000_output_function_epilogue): Do not handle "GNU Pascal". * config/rs6000/rs6000.c (rs6000_output_function_epilogue): Likewise. * config/sparc/sparc.c (sparc_pass_by_reference): Remove Pascal from documentation. Likewise. * dbxout.c (dbxout_range_type): Likewise. * doc/cpp.texi: Likewise. * doc/extend.texi: Likewise. * doc/frontends.texi: Likewise. * doc/invoke.texi: Remove Pascal entry. * tree.def (CLEANUP_POINT_EXPR): Likewise. * doc/rtl.texi (MODE_FUNCTION): Remove not used entry. 2018-09-25 Martin Liska * c-common.c (c_common_truthvalue_conversion): Remove Pascal from documentation. From-SVN: r264559 --- gcc/doc/cpp.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gcc/doc/cpp.texi') diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi index efad2c8..5345574 100644 --- a/gcc/doc/cpp.texi +++ b/gcc/doc/cpp.texi @@ -194,7 +194,7 @@ will be removed, and the Makefile will not work. Having said that, you can often get away with using cpp on things which are not C@. Other Algol-ish programming languages are often safe -(Pascal, Ada, etc.) So is assembly, with caution. @option{-traditional-cpp} +(Ada, etc.) So is assembly, with caution. @option{-traditional-cpp} mode preserves more white space, and is otherwise more permissive. Many of the problems can be avoided by writing C or C++ style comments instead of native language comments, and keeping macros simple. -- cgit v1.1