Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Elad Lahav <e2lahav@gmail.com>, perfbook@vger.kernel.org
Subject: Re: Section 4.2: wrong error reporting for pthread functions
Date: Wed, 18 Jul 2018 11:44:15 -0700	[thread overview]
Message-ID: <20180718184415.GF12945@linux.vnet.ibm.com> (raw)
In-Reply-To: <466d5063-ff10-af62-4867-88fa2db90af6@gmail.com>

On Wed, Jul 18, 2018 at 10:42:45PM +0900, Akira Yokosawa wrote:
> On 2018/07/18 06:14:48 -0700, Paul E. McKenney wrote:
> > On Wed, Jul 18, 2018 at 09:15:12PM +0900, Akira Yokosawa wrote:
> >> On 2018/07/17 09:15:31 -0700, Paul E. McKenney wrote:
> >>> On Wed, Jul 18, 2018 at 12:43:16AM +0900, Akira Yokosawa wrote:
> [...]
> >>>> So in theory, we can do what you want, but need somewhat ad-hoc
> >>>> manual tweaks. Still, it might be possible to write a script or two
> >>>> to do such tweaks in a semi-automated way.
> >>>
> >>> I already use scripts to do the auto-numbering and auto-intenting
> >>> for the old-style listings, so why not?  ;-)
> >>>
> >>> If I haven't already made these available, please let me know and
> >>> I can send them on.  They aren't exactly profound.
> >>
> >> So, there are 3 symbolic links under utilities/ in the Git repo:
> >>
> >>     c2latex.sh -> /home/paulmck/bin/c2latex.sh
> >>     extractClatex.sh -> /home/paulmck/bin/extractClatex.sh
> >>     latex2c.sh -> /home/paulmck/bin/latex2c.sh
> >>
> >> Now I know why I have no idea how you manage code snippets. ;-)
> > 
> > Heh!  I extract the code by hand and remove comments and any resulting
> > extraneous blank lines.  I run it through c2latex.sh, and occasionally
> > need to manually fix indentation.  Then I do any needed renumbering
> > manually in the text.
> > 
> > And latex2c.sh is more or less the inverse of c2latex.sh.
> 
> Well, I mean if you don't mind, I'd like to see those scripts
> in the Git repo rather than the symbolic links.

Hmmm...  I must admit that those symbolic links are a bit useless
outside of my laptop.  I have replaced them with the scripts themselves.
Please note that I haven't really used extractClatex.sh, though it did
seem like a good idea at the time.  :-/

							Thanx, Paul

>         Thanks, Akira
> 
> > 
> >>>> If you'd like to see what the code snippet and reference to labels
> >>>> would be,  I can prepare a experimental branch which is relative to
> >>>> commit f2b9d37d3b95 ("count: Expand on gap between C11 atomics and
> >>>> the Linux kernel").
> >>>>
> >>>> Thoughts?
> >>>
> >>> Sounds worth a try, thank you!
> >>
> >> OK.
> >> I'll send a pseudo pull request when it is ready.
> >> Hopefully in a couple of days.
> > 
> > Sounds good!
> > 
> > 							Thanx, Paul
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe perfbook" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 


  reply	other threads:[~2018-07-18 19:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 12:59 Section 4.2: wrong error reporting for pthread functions Elad Lahav
2018-07-14 23:33 ` Paul E. McKenney
2018-07-16 15:42   ` Akira Yokosawa
2018-07-16 16:39     ` Paul E. McKenney
2018-07-17 15:43       ` Akira Yokosawa
2018-07-17 16:15         ` Paul E. McKenney
2018-07-18 12:15           ` Akira Yokosawa
2018-07-18 13:14             ` Paul E. McKenney
2018-07-18 13:42               ` Akira Yokosawa
2018-07-18 18:44                 ` Paul E. McKenney [this message]
     [not found]     ` <CAJbg=FW7vpepT_0wq+ffpQBHgKX+s1ruDb5Bs-m3FCPHKcPV3A@mail.gmail.com>
2018-07-16 23:51       ` Akira Yokosawa
2018-07-17 11:05         ` Elad Lahav
2018-07-17 16:27           ` Paul E. McKenney

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=20180718184415.GF12945@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=e2lahav@gmail.com \
    --cc=perfbook@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox