On 1/9/26 11:36, Jakub Jelinek wrote:
Hi!
We miss quite a few -x option arguments that can be specified.
Ok for trunk?
This is fine in terms of content, but I have some nit-picky concerns
about formatting.
--- gcc/doc/invoke.texi.jj 2026-01-08 23:03:09.033192096 +0100
+++ gcc/doc/invoke.texi 2026-01-09 19:00:48.823455681 +0100
@@ -1752,14 +1752,19 @@ the next @option{-x} option. Possible v
@smallexample
c c-header cpp-output
c++ c++-header c++-system-header c++-user-header c++-cpp-output
-objective-c objective-c-header objective-c-cpp-output
-objective-c++ objective-c++-header objective-c++-cpp-output
+c++-system-module
+objective-c objective-c-header objective-c-cpp-output objc-cpp-output
+objective-c++ objective-c++-header objective-c++-cpp-output objc++-cpp-output
It would be good to consistently use two spaces between items in this
list, but I am afraid this line may end up being too long and overflow
the right margin in the PDF output. Can you either check that it
doesn't, or split it into two shorter lines?
assembler assembler-with-cpp
-ada
+ada adascil adawhy
cobol
d
f77 f77-cpp-input f95 f95-cpp-input
Likewise consistently use two spaces on this line too.
go
+modula-2 modula-2-cpp-output
+rust
+algol68
+lto
@end smallexample
Note that @option{-x} does not imply a particular language standard.
Jakub
-Sandra
