From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Timo Myyrä" <timo.myyra@bittivirhe.fi>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: add pthread_set_name_np support
Date: Sat, 27 Jun 2020 15:42:40 +0200 [thread overview]
Message-ID: <CAArVCkS8TFfpqmGYqENuMyk6t93yqAARDn+xmXBu83y+Lw8E4g@mail.gmail.com> (raw)
In-Reply-To: <83r1u03gtt.fsf@gnu.org>
Am Sa., 27. Juni 2020 um 13:10 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: timo.myyra@bittivirhe.fi (Timo Myyrä)
> > Date: Sat, 27 Jun 2020 13:49:24 +0300
> >
> > While browsing the emacs code I noticed that pthread_set_name_np is not
> > supported by emacs currently. Here's simple diff to add it.
> > I'm not that well versed in autoconf, probably should check pthread_set_name_np
> > within the pthread_setname_np block so both won't get enabled at the same time.
> >
> > Also I'm not sure if name should be padded, quickly looking OpenBSD sources
> > didn't indicate that padding would be required. LLVM code base seems to pad name
> > argument to max 16 chars on FreeBSD and 32 on OpenBSD.
> >
> > Thoughts?
>
> Thanks, we already have support for pthread_setname_np in what is soon
> going to be released as Emacs 27.1. Please take a look at the
> emacs-27 branch of the Emacs Git repository.
>
This is about pthread_set_name_np, not pthread_setname_np (note the underscore).
prev parent reply other threads:[~2020-06-27 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 10:49 add pthread_set_name_np support Timo Myyrä
2020-06-27 11:10 ` Eli Zaretskii
2020-06-27 12:51 ` Timo Myyrä
[not found] ` <C3EA421C-D39D-4FA3-A5EE-417E50E746AC@acm.org>
[not found] ` <87pn9kpenx.fsf@asteroid.bittivirhe.fi>
[not found] ` <4992EBB9-BEA9-4629-BCA5-462A252C86DC@acm.org>
[not found] ` <87lfk8p88e.fsf@asteroid.bittivirhe.fi>
[not found] ` <0C52F7EC-B5D1-493A-97C2-0A94AC9550BC@acm.org>
[not found] ` <87sgefdbhj.fsf@asteroid.bittivirhe.fi>
2020-06-28 9:38 ` Mattias Engdegård
2020-06-29 8:26 ` Robert Pluim
2020-06-27 13:42 ` Philipp Stephani [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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkS8TFfpqmGYqENuMyk6t93yqAARDn+xmXBu83y+Lw8E4g@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=timo.myyra@bittivirhe.fi \
/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.savannah.gnu.org/cgit/emacs.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).