From: Jeff King <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: "Ævar Arnfjörð Bjarmason" <email@example.com>, firstname.lastname@example.org, "Denton Liu" <email@example.com>, "Jeff Hostetler" <firstname.lastname@example.org>, "Johannes Schindelin" <Johannes.Schindelin@gmx.de> Subject: Re: [PATCH v3] trace2: refactor to avoid gcc warning under -O3 Date: Fri, 21 May 2021 05:34:18 -0400 [thread overview] Message-ID: <YKd+mtQuW9Yz0qwh@coredump.intra.peff.net> (raw) In-Reply-To: <email@example.com> On Fri, May 21, 2021 at 07:08:11AM +0900, Junio C Hamano wrote: > Jeff King <firstname.lastname@example.org> writes: > > >> @@ -287,7 +285,7 @@ static int tr2_dst_try_unix_domain_socket(struct tr2_dst *dst, > >> if (tr2_dst_want_warning()) > >> warning("trace2: could not connect to socket '%s' for '%s' tracing: %s", > >> path, tr2_sysenv_display_name(dst->sysenv_var), > >> - strerror(e)); > >> + strerror(errno)); > > > > We expect the value of errno to persist across tr2_dst_want_warning() > > and tr2_sysenv_display_name() here. The former may call getenv() and > > atoi(). I think that's probably fine, but if we wanted to be really > > paranoid, we'd have to preserve errno manually here, too. > > Being "really paranoid" consistently within the file would mean a > change like the attached, I would think, on top of what was posted. > > Or tr2_dst_want_warning() and tr2_sysenv_display_name() can be > taught to preserve errno like tr2_dst_dry_uds_connect() was taught > to do so by the patch under discussion, which may reduce the amount > of apparent change, but constantly moving the contents of errno > around just in case we later might want to use its value feels > dirty. > > I dunno. > > trace2/tr2_dst.c | 14 +++++++++++--- > 1 file changed, 11 insertions(+), 3 deletions(-) Ah, yeah. I didn't look to see if there were existing cases of the same thing. I could go either way on this kind of saved_errno thing in general (the tr2 functions called in between are really quite unlikely to set errno (I am not even sure if getenv() and atoi() can, so this really might just be future-proofing in case those tr2 functions get more complicated). But seeing that there are other cases of the same, I definitely think it is not something that should be in Ævar's patch. It is a cleanup we could do on top if we cared to. -Peff
prev parent reply other threads:[~2021-05-21 9:34 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-01 7:30 [PATCH] Fix -Wmaybe-uninitialized warnings under -O0 Denton Liu [not found] ` <CAPUEspgBkmxszgBee8C9hZnEwqztf-XKEj7LB_jWVFJaJCge0w@mail.gmail.com> 2020-04-01 9:05 ` Denton Liu 2020-04-01 9:52 ` Jeff King 2020-04-01 14:06 ` Denton Liu 2020-04-03 14:04 ` Jeff King 2020-04-03 14:38 ` Jeff King 2020-04-04 12:07 ` Denton Liu 2020-04-04 14:21 ` Jeff King 2021-05-05 8:40 ` [PATCH] trace2: refactor to avoid gcc warning under -O3 Ævar Arnfjörð Bjarmason 2021-05-05 9:47 ` Junio C Hamano 2021-05-05 13:34 ` Jeff King 2021-05-05 14:38 ` Johannes Schindelin 2021-05-06 1:26 ` Junio C Hamano 2021-05-06 20:29 ` Johannes Schindelin 2021-05-06 21:10 ` Junio C Hamano 2021-05-11 14:34 ` Johannes Schindelin 2021-05-11 18:00 ` Jeff King 2021-05-11 20:58 ` Junio C Hamano 2021-05-11 21:07 ` Jeff King 2021-05-11 21:33 ` Junio C Hamano 2021-05-11 7:03 ` Junio C Hamano 2021-05-11 13:04 ` [PATCH v2] " Ævar Arnfjörð Bjarmason 2021-05-11 16:40 ` Jeff Hostetler 2021-05-11 17:54 ` Jeff King 2021-05-11 18:08 ` Jeff King 2021-05-11 21:09 ` Junio C Hamano 2021-05-20 0:20 ` Junio C Hamano 2021-05-20 11:05 ` [PATCH v3] " Ævar Arnfjörð Bjarmason 2021-05-20 13:13 ` Jeff King 2021-05-20 22:08 ` Junio C Hamano 2021-05-21 9:34 ` Jeff King [this message]
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YKd+mtQuW9Yz0qwh@coredump.intra.peff.net \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v3] trace2: refactor to avoid gcc warning under -O3' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).