https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64094
Harald van Dijk <harald at gigawatt dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harald at gigawatt dot nl
--- Comment #2 from Harald van Dijk <harald at gigawatt dot nl> ---
GCC uses strerror (indirectly) for printing error messages, through the use of
%m with vfprintf. This is done in many separate locations. binutils has special
cases in the form of (if ENOENT then print custom message else print system
error).
The GNU Coding Standards
(http://www.gnu.org/prep/standards/html_node/Semantics.html) say:
> Include the system error text (from perror, strerror, or equivalent) in every
> error message resulting from a failing system call, as well as the name of
> the file if any and the name of the utility.
I do not personally care either way, but GCC's error message is in line with
those coding standards, and binutils's error message is not (even if it may be
in line with the intent of those coding standards, I make no comment on that).
Perhaps either GCC should be left as it is now, or if those coding standards do
not correctly reflect the intent, they should be changed first?
