On Jul 12 21:52, Christopher Faylor wrote:
On Wed, Jul 08, 2009 at 01:11:53AM +0100, Dave Korn wrote:
Dave Korn wrote:
It doesn't do anything about the reload failure, which is a bug in
GCC-3, since the usage is a standard usage supported by the
documentation. It's possible that it may
Corinna Vinschen wrote:
On Jul 12 21:52, Christopher Faylor wrote:
There is a subtle difference in the generated code if you do this:
--- winbase.h 7 Jul 2009 21:41:43 - 1.16
+++ winbase.h 13 Jul 2009 01:46:17 -
@@ -56,7 +56,7 @@
{
return
({
-register long
On Mon, Jul 13, 2009 at 10:36:03AM +0100, Dave Korn wrote:
Corinna Vinschen wrote:
On Jul 12 21:52, Christopher Faylor wrote:
There is a subtle difference in the generated code if you do this:
--- winbase.h 7 Jul 2009 21:41:43 - 1.16
+++ winbase.h 13 Jul 2009 01:46:17 -
@@
On Wed, Jul 08, 2009 at 01:11:53AM +0100, Dave Korn wrote:
Dave Korn wrote:
It doesn't do anything about the reload failure, which is a bug in
GCC-3, since the usage is a standard usage supported by the
documentation. It's possible that it may disappear as a side-effect,
in which case all the
On Jul 8 17:36, Dave Korn wrote:
Corinna Vinschen wrote:
On Jul 8 01:11, Dave Korn wrote:
But seriously, I'm still using gcc 4.3.2 20080827 (alpha-testing) 1
for building Cygwin. Is that sufficient for now or should I upgrade?
That's 4.3.2-1, no?
Uh, yes. It's the version I used
On Jul 8 01:11, Dave Korn wrote:
Dave Korn wrote:
It doesn't do anything about the reload failure, which is a bug in GCC-3,
since the usage is a standard usage supported by the documentation. It's
possible that it may disappear as a side-effect, in which case all the
better.
Corinna Vinschen wrote:
On Jul 8 01:11, Dave Korn wrote:
But seriously, I'm still using gcc 4.3.2 20080827 (alpha-testing) 1
for building Cygwin. Is that sufficient for now or should I upgrade?
That's 4.3.2-1, no? I've been using nothing but 4.3.2-2 for a while now.
The problems are
On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote:
Brian Ford wrote:
I'm trying to build Cygwin 1.7 from CVS to debug an ImageMagick problem on
server 2008 that causes an access violation in cygwin1.dll. Doe anyone
know the work around for this issue?
g++ (GCC) 3.4.4 (cygming
Christopher Faylor wrote:
On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote:
winsup/cygwin/ChangeLog:
* winbase.h (ilockexch): Avoid making 'ret' volatile.
(ilockcmpexch): Likewise.
Ok?
Yes. Thanks.
Applied, and I even caught the changelog formatting in time!
On Tue, Jul 07, 2009 at 10:55:13PM +0100, Dave Korn wrote:
Christopher Faylor wrote:
On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote:
winsup/cygwin/ChangeLog:
* winbase.h (ilockexch): Avoid making 'ret' volatile.
(ilockcmpexch): Likewise.
Ok?
Yes. Thanks.
Dave Korn wrote:
It doesn't do anything about the reload failure, which is a bug in GCC-3,
since the usage is a standard usage supported by the documentation. It's
possible that it may disappear as a side-effect, in which case all the better.
Nope, no such luck.
Also, the libstdc++
11 matches
Mail list logo
