zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>,
	"Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: 5.8: LTO exposes some new issues
Date: Tue, 28 Jul 2020 08:09:27 +0000	[thread overview]
Message-ID: <20200728080927.40153d11@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAN=4vMrfmPBoS9i5aCSZA5bPuPnjboZ7BNN7poDGPy9ra3BeKQ@mail.gmail.com>

Roman Perepelitsa wrote on Mon, 27 Jul 2020 16:19 +0200:
> FYI: I won't be doing anything about the warning in gettempname (which
> I'm not getting with my toolchain).

I'm not sure there's anything we can do about that warning.  When I last
looked, the issue was that:

- The linker emits the warning whenever mktemp(3) is used;

- At least one callsite uses mktemp(3) unavoidably: it follows the call
  not by open(2) but by mknod(2), so the warning's rationale (that
  mkstemp(3) should be used in lieu of mktemp(3)) does not apply;

- The linker gives no way to disable the warning.

Unless there's an alternative to mktemp(3)+mknod(2) that I'm unaware
of, I'd triage this as a linker bug, in that it should be possible to
silence the warning when it's a false positive.

Cheers,

Daniel

  reply	other threads:[~2020-07-28  8:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 23:41 Tomasz Kłoczko
2020-07-22  5:59 ` Daniel Shahaf
2020-07-25 17:43   ` Bart Schaefer
     [not found]     ` <CABB28CxSD5w-SY-iCVYuQ4kJfBpNJOWhpk4HOrS1DNPfMVztgw@mail.gmail.com>
2020-07-25 20:05       ` Fwd: " Bart Schaefer
2020-07-27  2:12         ` Daniel Shahaf
2020-07-27 10:07           ` Tomasz Kłoczko
2020-07-27 11:09             ` Roman Perepelitsa
2020-07-27 12:19               ` Roman Perepelitsa
2020-07-27 12:46                 ` Tomasz Kłoczko
2020-07-27 14:13                   ` Roman Perepelitsa
2020-07-27 14:19                   ` Roman Perepelitsa
2020-07-28  8:09                     ` Daniel Shahaf [this message]
2020-07-28 10:55                     ` Roman Perepelitsa
2020-07-28  8:19                   ` Daniel Shahaf
2020-07-28  7:53                 ` Daniel Shahaf
2020-07-28  8:25                   ` Peter Stephenson
2020-07-28 10:52                     ` Roman Perepelitsa
2020-07-28 11:19                       ` Daniel Shahaf
2020-07-28 11:31                         ` Roman Perepelitsa
2020-07-28 11:51                           ` Daniel Shahaf

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=20200728080927.40153d11@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=kloczko.tomasz@gmail.com \
    --cc=roman.perepelitsa@gmail.com \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).