From: Ross Johnson <rpj@ise.canberra.edu.au>
To: pthreads-win32@sources.redhat.com
Cc: Bryan.Montross@ieee.org
Subject: [Fwd: 64-Bit pthreads]
Date: Thu, 20 Sep 2001 20:18:00 -0000 [thread overview]
Message-ID: <3BAAB17C.70A60FEF@ise.canberra.edu.au> (raw)
I'm forwarding your questions to the list in case someone
has been there already and is able to help.
It's not clear from your message whether you've tried
building the library from source. The list may be better
able to help with specific problems that arise from doing
that.
One area I would expect a problem is in cancel.c. That is,
the #defines at the top of the file used later by the
routine ptw32_cancel_thread(). This is the only hardware
dependent code in the library.
Regards.
Ross
"BRYAN A. MONTROSS" wrote:
>
> I am currently working on a multi-threaded application on a Windows2000
> platform. I have been working on making my code platform independent so
> it will run on both Windows and Unix operating systems. At the same time
> I am attempting to port all of my code to the new 64-bit architecture
> (Intel's Itanium processor). One of the problems I am running into is the
> libraries created for pthreads are 32-bit libraries and I need them to be
> 64-bit in order for them to work on my new machine. Have there been any
> efforts to port pthreads to 64-bits on a Windows platform? If not, do you
> know what needs to be done to make pthreads runnable on WindowsXP 64-Bit
> Edition? I would appreciate any help I can get on this subject matter,
> even if it means that I have to change to a new thread class.
>
> Thanks,
> --Bryan Montross
> Bryan.Montross@ieee.org
reply other threads:[~2001-09-20 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BAAB17C.70A60FEF@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=Bryan.Montross@ieee.org \
--cc=pthreads-win32@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).