From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Cc: serge.guelton@telecom-bretagne.eu
Subject: RFC: Document unexpected behaviour of --fatal-warnings
Date: Tue, 23 Jan 2024 12:28:17 +0000 [thread overview]
Message-ID: <87fryomdy6.fsf@redhat.com> (raw)
Hi Guys,
It was recently pointed out to me that the bfd linker's
--fatal-warnings option can behave in an unexpected manner. For
example:
$ ld.bfd -z bad-option --fatal-warnings -e 0/dev/null
ld.bfd: warning: -z bad-option ignored
$ echo $?
0
ie the warning about the ignored option is not being treated as an
error. This happens because the --fatal-warnings option only takes
affect after it has been processed, and we process the options in a
linear order. So the following works:
$ ld.bfd --fatal-warnings -z bad-option -e 0 /dev/null
ld.bfd: warning: -z bad-option ignored
$ echo $?
1
This behaviour differs from gold and lld, both of which honour
--fatal-warnings no matter where it occurs on the command line.
So we could fix the linker, create a two pass argument scan and the
problem would be solved. But a) I am lazy and b) we already have a
precedent for options on the command line only affecting options that
come after it. (I am thinking of the -L option here, although there
are probably several others). So instead I am considering documenting
the current behaviour as expected. (See the patch below).
What do people think ?
Cheers
Nick
diff --git a/ld/ld.texi b/ld/ld.texi
index 4fda259a552..16ab08e03f2 100644
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -1993,7 +1993,20 @@ in filename invoked by -R or --just-symbols
@item --fatal-warnings
@itemx --no-fatal-warnings
Treat all warnings as errors. The default behaviour can be restored
-with the option @option{--no-fatal-warnings}.
+with the option @option{--no-fatal-warnings}. Note: this option does
+not affects warnings generated by other command line options that are
+placed before it on the command line. So for example:
+
+@smallexample
+$ ld -z bad-option --fatal-warnings -e 0/dev/null
+ld: warning: -z bad-option ignored
+$ echo $?
+0
+$ ld --fatal-warnings -z bad-option -e 0 /dev/null
+ld: warning: -z bad-option ignored
+$ echo $?
+1
+@end smallexample
@kindex -w
@kindex --no-warnings
next reply other threads:[~2024-01-23 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 12:28 Nick Clifton [this message]
2024-01-23 12:38 ` Jan Beulich
2024-01-23 12:50 ` H.J. Lu
2024-01-23 13:15 ` H.J. Lu
2024-01-24 15:07 ` Serge Guelton
2024-01-24 15:13 ` Sam James
2024-01-24 16:06 ` H.J. Lu
2024-01-24 22:52 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fryomdy6.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=serge.guelton@telecom-bretagne.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).