From: Thomas Rast <trast@student•ethz.ch>
To: Jim Meyering <jim@meyering•net>
Cc: "Richard W.M. Jones" <rjones@redhat•com>,
Markus Trippelsdorf <markus@trippelsdorf•de>,
<git@vger•kernel.org>, "Shawn O. Pearce" <spearce@spearce•org>,
Jeff King <peff@peff•net>, Nicolas Pitre <nico@fluxnic•net>
Subject: Re: general protection faults with "git grep" version 1.7.7.1
Date: Tue, 25 Oct 2011 18:07:53 +0200 [thread overview]
Message-ID: <201110251807.53893.trast@student.ethz.ch> (raw)
In-Reply-To: <201110251800.28054.trast@student.ethz.ch>
Thomas Rast wrote:
> Jim Meyering wrote:
> > Thomas Rast wrote:
> > > [GCC moves access to a file-static variable across pthread_mutex_lock()]
> >
> > Thanks for the investigation.
> > Actually, isn't gcc -O2's code-motion justified?
> > While we *know* that those globals may be modified asynchronously,
> > builtin/grep.c forgot to tell gcc about that.
>
> I'm somewhat unwilling to believe that:
>
> * "volatile" enforces three unrelated things, see e.g. [1].
Argh, forgot my reference:
[1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2016.html
section "Existing portable uses"
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2011-10-25 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 20:11 general protection faults with "git grep" version 1.7.7.1 Markus Trippelsdorf
2011-10-24 21:49 ` Richard W.M. Jones
2011-10-24 22:58 ` Markus Trippelsdorf
2011-10-25 0:00 ` Bernt Hansen
2011-10-25 5:53 ` Jeff King
2011-10-25 11:11 ` Bernt Hansen
2011-10-25 13:50 ` Thomas Rast
2011-10-25 15:17 ` Jim Meyering
2011-10-25 15:32 ` Markus Trippelsdorf
2011-10-25 16:00 ` Thomas Rast
2011-10-25 16:07 ` Thomas Rast [this message]
2011-10-25 16:37 ` Jim Meyering
2011-10-25 16:54 ` Thomas Rast
2011-10-25 20:24 ` Jim Meyering
2011-10-25 15:37 ` Jeff King
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=201110251807.53893.trast@student.ethz.ch \
--to=trast@student$(echo .)ethz.ch \
--cc=git@vger$(echo .)kernel.org \
--cc=jim@meyering$(echo .)net \
--cc=markus@trippelsdorf$(echo .)de \
--cc=nico@fluxnic$(echo .)net \
--cc=peff@peff$(echo .)net \
--cc=rjones@redhat$(echo .)com \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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