From: Nenad Vukicevic <nenad@intrepid.com>
To: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: multi-{inferior,exec}
Date: Tue, 07 Sep 2010 21:50:00 -0000 [thread overview]
Message-ID: <4C86B3AA.8010503@intrepid.com> (raw)
In-Reply-To: <20100907213421.GA21182@caradoc.them.org>
On 9/7/2010 2:34 PM, Daniel Jacobowitz wrote:
> On Tue, Sep 07, 2010 at 11:03:48AM -0600, Tom Tromey wrote:
>> This sounds like the "barrier" feature in HPD.
>> A patch for this would be interesting, too.
>>
>> I am curious though -- what is it useful for?
> Think about this in terms of, for example, automatically parallelized
> OpenMP code. If you have a parallel region, it's handy to examine all
> threads at that point. I don't know if this would work better in UPC
> than it would in OpenMP though; you can have code executed in only
> some threads...
>
Also, think about 32 or more threads printing breakpoint announcments.
:) As all
UPC threads execute the same code, but work on different sets of data,
you look at all of them as only one program.
UPC has a "upc_barrier" statement that all threads need to arrive before
going forward. At that point your shared space is consistent and it is a
natural
place to stop.
Nenad
next prev parent reply other threads:[~2010-09-07 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 22:41 multi-{inferior,exec} Tom Tromey
2010-09-04 6:26 ` multi-{inferior,exec} Jan Kratochvil
2010-09-05 17:16 ` multi-{inferior,exec} Nenad Vukicevic
2010-09-07 17:04 ` multi-{inferior,exec} Tom Tromey
2010-09-07 21:34 ` multi-{inferior,exec} Daniel Jacobowitz
2010-09-07 21:50 ` Nenad Vukicevic [this message]
2010-09-10 21:56 ` multi-{inferior,exec} Tom Tromey
2010-09-10 23:07 ` multi-{inferior,exec} Stan Shebs
2010-09-11 1:46 ` multi-{inferior,exec} Tom Tromey
2010-09-10 22:52 ` multi-{inferior,exec} Stan Shebs
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=4C86B3AA.8010503@intrepid.com \
--to=nenad@intrepid.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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