public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Vincent Sweeney <v.sweeney@barrysworld.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: snapshot-2002-03-02 available
Date: Sat, 02 Mar 2002 19:56:00 -0000	[thread overview]
Message-ID: <3C819EC7.A9B3F6BB@ise.canberra.edu.au> (raw)
In-Reply-To: <006501c1c1de$60d496d0$0201010a@frodo>

Thanks. Although it isn't necessary to specify pthread.def anymore,
which has therefore been removed from the package.

You can also replace all source files with just pthread.c. This
#includes all other source files. The reason for this is to
maximise the potential for inlining under /O2. (As I understand it,
inlining can only occur within the same "translation unit".)

Unfortunately it then seems there is no way to list all of the
individual source files (so they can be edited) except by
running a build and then looking in the "External references"
folder. Is there a way to gerate the external references list
without running a build?

Ross

Vincent Sweeney wrote:
> 
> The included MSVC++ project files do not work / compile this snapshot.
> Attached are some updated files that build the project without any problems.
> 
> Regards,
>     Vince.
> 
> ----- Original Message -----
> From: "Ross Johnson" <rpj@ise.canberra.edu.au>
> To: <pthreads-win32@sources.redhat.com>
> Sent: Saturday, March 02, 2002 6:24 AM
> Subject: NEW: snapshot-2002-03-02 available
> 
> > There are bugs fixes, new routines, new tests, and a lot
> > of reorganisation. Please see the ANNOUNCE, NEWS, and BUGS
> > files in the package or at:
> >
> > http://sources.redhat.com/pthreads-win32/announcement.html
> >
> > There is also an updated Copyright notice on the source
> > code, but NO CHANGE to the licensing, which is the GNU LGPL.
> >
> > The Copyright notice replaces the original inadequate notice
> > and reflects the heritage of the project.
> >
> > The Copyright notice is slightly different to the one that I
> > proposed on this list a few months back. This change was at
> > my own instigation. I don't expect anyone to have any
> > objection to it since there was no objection to the previous
> > one, but please let me know if you do.
> >
> > I've also made acknowledgements more prominent in the
> > CONTRIBUTORS file and ChangeLog to go with the change in the
> > copyright notice. Let me know if I've missed you out, or
> > missed noting any significant contributions.
> >
> > Enjoy!
> > Ross
> >
> 
>   ------------------------------------------------------------------------
>                        Name: pthread-msvc.zip
>    pthread-msvc.zip    Type: Zip Compressed Data (application/x-zip-compressed)
>                    Encoding: base64

  reply	other threads:[~2002-03-03  3:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 22:24 NEW: " Ross Johnson
2002-03-02  3:35 ` Vincent Sweeney
2002-03-02 19:56   ` Ross Johnson [this message]
2002-03-05 18:35     ` Scott McCaskill
2002-03-04  7:01 Crescioli, Phil
2002-03-04 14:57 ` Ross Johnson
2002-03-29 10:59 Crescioli, Phil
2002-04-01  6:13 Aurelio Medina

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=3C819EC7.A9B3F6BB@ise.canberra.edu.au \
    --to=rpj@ise.canberra.edu.au \
    --cc=pthreads-win32@sources.redhat.com \
    --cc=v.sweeney@barrysworld.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).