From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [PATCH] git grep: be careful to use mutices only when they are initialized
Date: Thu, 27 Oct 2011 11:02:51 -0700 [thread overview]
Message-ID: <20111027180251.GE1967@sigill.intra.peff.net> (raw)
In-Reply-To: <7v39ef34in.fsf@alter.siamese.dyndns.org>
On Wed, Oct 26, 2011 at 01:02:40PM -0700, Junio C Hamano wrote:
> - Could we lose "#ifndef NO_PTHREADS" inside grep_sha1(), grep_file(),
> and possibly cmd_grep() functions and let the compiler optimize things
> away under NO_PTHREADS compilation?
I don't think so. If NO_PTHREADS is set, we might not have pthread
functions at all. Sure, many compilers will optimize:
if (0)
pthread_mutex_lock(...);
to remove the call completely. But would a compiler be wrong to complain
that pthread_mutex_lock is not defined, or to include reference to it
for the linker? gcc, both with and without optimizations, will complain
about:
echo 'int main() { if (0) does_not_exist(); return 0; }' >foo.c
gcc -Wall -c foo.c
though it does actually remove the dead code and link properly. I
wouldn't be surprised if some other compilers don't work, though (and of
course the warning is ugly).
I think you would have to do something like this in thread-utils.h:
#ifndef NO_PTHREADS
#include <pthread.h>
#else
#define pthread_mutex_t int
#define pthread_mutex_init(m, a) do {} while(0)
#define pthread_mutex_lock(m) do {} while(0)
#define pthread_mutex_unlock(m) do {} while (0)
/* and so forth for every pthread function */
#endif
-Peff
prev parent reply other threads:[~2011-10-27 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 17:25 [PATCH] git grep: be careful to use mutices only when they are initialized Johannes Schindelin
2011-10-26 9:10 ` [msysGit] " Tay Ray Chuan
2011-10-26 15:42 ` Johannes Schindelin
2011-10-26 9:19 ` Pat Thoyts
2011-10-26 17:17 ` Junio C Hamano
2011-10-26 18:57 ` Johannes Schindelin
2011-10-26 20:02 ` Junio C Hamano
2011-10-26 20:04 ` Junio C Hamano
2011-10-26 20:08 ` Junio C Hamano
2011-10-27 15:27 ` René Scharfe
2011-10-27 18:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111027180251.GE1967@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
/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.
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).