Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
e54655a2
Commit
e54655a2
authored
Apr 16, 2010
by
Diego Novillo
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify what happens with an unrecognized -Wno- option
From-SVN: r158413
parent
68a3eb69
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
gcc/doc/invoke.texi
+9
-0
No files found.
gcc/doc/invoke.texi
View file @
e54655a2
...
...
@@ -2807,6 +2807,15 @@ two forms, whichever is not the default. For further,
language-specific options also refer to @ref{C++ Dialect Options} and
@ref{Objective-C and Objective-C++ Dialect Options}.
When an unrecognized warning label is requested, for example
@option{-Wunknwon-warning}, GCC will emit a diagnostic stating
that the option is not recognized. However, if the @samp{-Wno-} form
is used, the behavior is slightly different: No diagnostic will be
produced for @option{-Wno-unknown-warning} unless other diagnostics
are being produced. This allows the use of new @option{-Wno-} options
with old compilers, but if something goes wrong, the compiler will
warn that an unrecognized option was used.
@table @gcctabopt
@item -pedantic
@opindex pedantic
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment