From: "Eugéne Suter" <easuter@gmail.com>
To: tprince@computer.org
Cc: gcc-help@gcc.gnu.org
Subject: Re: running OpenMP-enabled programs: segmentation fault
Date: Mon, 16 Feb 2009 11:12:00 -0000 [thread overview]
Message-ID: <6bb01940902160308w190947bhf9677099d30986e2@mail.gmail.com> (raw)
In-Reply-To: <4998EC28.80807@sbcglobal.net>
2009/2/16 Tim Prince <TimothyPrince@sbcglobal.net>:
> Eugéne Suter wrote:
>> snipped, as much rambling stuff as the following reply:
> I hesitate to respond, as I can see reasons for Tbird to be putting you in
> the spam box.
Please feel free to do so. I probably should have mentioned that I'm
new to OpenMP and shared memory programming in general. So it was a
bit hasty of me to post one of my first problems here.
Sorry for the inconvenience.
prev parent reply other threads:[~2009-02-16 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 10:34 Eugéne Suter
2009-02-16 4:32 ` Tim Prince
2009-02-16 11:12 ` Eugéne Suter [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=6bb01940902160308w190947bhf9677099d30986e2@mail.gmail.com \
--to=easuter@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tprince@computer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).