diff options
author | Nick Alcock <nick.alcock@oracle.com> | 2024-04-12 14:46:00 +0100 |
---|---|---|
committer | Nick Alcock <nick.alcock@oracle.com> | 2024-04-19 16:14:48 +0100 |
commit | 7e1368b58f37f89152c5811eab98f4667d807b04 (patch) | |
tree | 1bf4045835c57a18d604ea341ce64256836a05b6 /binutils | |
parent | b5ac272b872db997adc184b23da74f755d4b8f08 (diff) | |
download | gdb-7e1368b58f37f89152c5811eab98f4667d807b04.zip gdb-7e1368b58f37f89152c5811eab98f4667d807b04.tar.gz gdb-7e1368b58f37f89152c5811eab98f4667d807b04.tar.bz2 |
libctf: don't pass errno into ctf_err_warn so often
The libctf-internal warning function ctf_err_warn() can be passed a libctf
errno as a parameter, and will add its textual errmsg form to the passed-in
error message. But if there is an error on the fp already, and this is
specifically an error and not a warning, ctf_err_warn() will print the error
out regardless: there's no need to pass in anything but 0.
There are still a lot of places where we do
ctf_err_warn (fp, 0, EFOO, ...);
return ctf_set_errno (fp, 0, EFOO);
I've left all of those alone, because fixing it makes the code a bit longer:
but fixing the cases where no return is involved and the error has just been
set on the fp itself costs nothing and reduces redundancy a bit.
libctf/
* ctf-dedup.c (ctf_dedup_walk_output_mapping): Drop the errno arg.
(ctf_dedup_emit): Likewise.
(ctf_dedup_type_mapping): Likewise.
* ctf-link.c (ctf_create_per_cu): Likewise.
(ctf_link_deduplicating_close_inputs): Likewise.
(ctf_link_deduplicating_one_symtypetab): Likewise.
(ctf_link_deduplicating_per_cu): Likewise.
* ctf-lookup.c (ctf_lookup_symbol_idx): Likewise.
* ctf-subr.c (ctf_assert_fail_internal): Likewise.
Diffstat (limited to 'binutils')
0 files changed, 0 insertions, 0 deletions