[prev in list] [next in list] [prev in thread] [next in thread]
List: mingw-notify
Subject: MinGW-notify digest, Vol 1 #875 - 2 msgs
From: mingw-notify-request () lists ! sourceforge ! net
Date: 2004-08-13 3:43:43
Message-ID: E1BvT3k-0007TC-Fm () sc8-sf-list1 ! sourceforge ! net
[Download RAW message or body]
Send MinGW-notify mailing list submissions to
mingw-notify@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
mingw-notify-request@lists.sourceforge.net
You can reach the person managing the list at
mingw-notify-admin@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-notify digest..."
This list is used to send updates of submitted patches, bug reports and file \
releases. You are discouraged from posting to this list. If you wish to unsubscribe \
you can do so at https://lists.sourceforge.net/lists/listinfo/mingw-notify.
Today's Topics:
1. [ mingw-Bugs-1008330 ] movaps problem with mingw (SourceForge.net)
2. [ mingw-Bugs-1008330 ] movaps problem with mingw (SourceForge.net)
--__--__--
Message: 1
To: noreply@sourceforge.net
From: "SourceForge.net" <noreply@sourceforge.net>
Date: Thu, 12 Aug 2004 15:43:27 -0700
Subject: [Mingw-notify] [ mingw-Bugs-1008330 ] movaps problem with mingw
Bugs item #1008330, was opened at 2004-08-12 22:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1008330&group_id=2435
Category: MinGW
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matt Daws (mattdaws)
Assigned to: Earnie Boyd (earnie)
Summary: movaps problem with mingw
Initial Comment:
I have a slightly complicated program which is crashing
when I compile with certain options. I have narrowed
the problem down to the fact that MinGW is generating
MOVAPS instructions which are trying to access memory
at an unaligned point. If I edit the assembler file
and replace these with MOVUPS instructions and then
assemble and link, my program works fine.
I thought this was linked to my use of threads and/or
the printf instruction. However, I've removed the
printf's and still get the problem. I am now
suspecting my use of threads. I tried changing from
using CreateThread to using _beginthreadex, but this
didn't help.
A Google search reveals that other people have been
having a general problem with GCC, MOVAPS and threads.
Thus this *might* be a problem with GCC. However,
people in the know are blaming the problem on system
calls which are not setting up the stack in an aligned
manner when starting a thread. Hence my hope that
_beginthreadex would help.
The problem does not occur with Mingw 3.3.3, but this
seems to be down to the fact that the compiler no
longer produces MOVAPS instructions.
I am using Mingw 3.4.1, Windows XP SP1. The compiler
flags I use are:
-Wall -ffast-math -O3 -march=pentium4 -mthreads
But anything enabling SSE seems to give problems.
I could send the code, but it is rather long. I could
also try to generate a smaller example which does the
same thing, but perhaps the bug will not occur.
Here is a snippit of the offending assembly (produced
with the -S flag in g++):
__ZN9Landscape4DrawEv:
pushl %ebp
movl %esp, %ebp
pushl %edi
pushl %esi
pushl %ebx
subl $236, %esp
movl 8(%ebp), %edi
flds 8(%edi)
flds 40(%edi)
.....
movaps %xmm4, -104(%ebp)
.....
movaps %xmm0, -136(%ebp)
Many thanks in advance for any hints! --Matt Daws
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1008330&group_id=2435
--__--__--
Message: 2
To: noreply@sourceforge.net
From: "SourceForge.net" <noreply@sourceforge.net>
Date: Thu, 12 Aug 2004 18:31:09 -0700
Subject: [Mingw-notify] [ mingw-Bugs-1008330 ] movaps problem with mingw
Bugs item #1008330, was opened at 2004-08-13 10:43
Message generated for change (Comment added) made by dannysmith
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1008330&group_id=2435
Category: MinGW
Group: None
> Status: Closed
> Resolution: Duplicate
Priority: 5
Submitted By: Matt Daws (mattdaws)
Assigned to: Earnie Boyd (earnie)
Summary: movaps problem with mingw
Initial Comment:
I have a slightly complicated program which is crashing
when I compile with certain options. I have narrowed
the problem down to the fact that MinGW is generating
MOVAPS instructions which are trying to access memory
at an unaligned point. If I edit the assembler file
and replace these with MOVUPS instructions and then
assemble and link, my program works fine.
I thought this was linked to my use of threads and/or
the printf instruction. However, I've removed the
printf's and still get the problem. I am now
suspecting my use of threads. I tried changing from
using CreateThread to using _beginthreadex, but this
didn't help.
A Google search reveals that other people have been
having a general problem with GCC, MOVAPS and threads.
Thus this *might* be a problem with GCC. However,
people in the know are blaming the problem on system
calls which are not setting up the stack in an aligned
manner when starting a thread. Hence my hope that
_beginthreadex would help.
The problem does not occur with Mingw 3.3.3, but this
seems to be down to the fact that the compiler no
longer produces MOVAPS instructions.
I am using Mingw 3.4.1, Windows XP SP1. The compiler
flags I use are:
-Wall -ffast-math -O3 -march=pentium4 -mthreads
But anything enabling SSE seems to give problems.
I could send the code, but it is rather long. I could
also try to generate a smaller example which does the
same thing, but perhaps the bug will not occur.
Here is a snippit of the offending assembly (produced
with the -S flag in g++):
__ZN9Landscape4DrawEv:
pushl %ebp
movl %esp, %ebp
pushl %edi
pushl %esi
pushl %ebx
subl $236, %esp
movl 8(%ebp), %edi
flds 8(%edi)
flds 40(%edi)
.....
movaps %xmm4, -104(%ebp)
.....
movaps %xmm0, -136(%ebp)
Many thanks in advance for any hints! --Matt Daws
----------------------------------------------------------------------
> Comment By: Danny Smith (dannysmith)
Date: 2004-08-13 13:31
Message:
Logged In: YES
user_id=11494
Duplicate of 1001932, which has a self-contained testcase.
The bug has also been reported to GCC's bugzilla,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16890
but no response yet.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1008330&group_id=2435
--__--__--
_______________________________________________
MinGW-notify mailing list
MinGW-notify@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-notify
End of MinGW-notify Digest
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic