public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Sébastien Kunz-Jacques" <kunzjacq@yahoo.fr>
To: pthreads-win32@sourceware.org
Subject: Re: pthreads-win32 2.8.0, stack alignment, and SSE code
Date: Sun, 05 Oct 2008 20:12:00 -0000	[thread overview]
Message-ID: <48E91F80.5080809@yahoo.fr> (raw)
In-Reply-To: <48E91469.3060508@lisha.ufsc.br>

Ramiro Polla a écrit :
>> Ramiro Polla a écrit :
>> I didn't express myself very well then. I meant to say: "The overhead 
>> really is negligible. Starting the thread takes much longer, so the 
>> overhead in aligning the stack gets hidden away in the delay to start 
>> the thread".
In that case always aligning the stack in threadStart would save some 
headaches to a lot of people, I think. While googling about these issues 
I found mentions of the ffmpeg case you talked about; that is because of 
them that I found the correct attribute to align the stack. some mplayer 
codecs seem to have trouble with these multithreaded alignment issues too.

If for some reason it is not desirable to patch the lib, would it be 
possible to have some easy to see disclaimer added about this problem 
somewhere?

  reply	other threads:[~2008-10-05 20:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 12:32 Sébastien Kunz-Jacques
2008-10-05 13:41 ` Ramiro Polla
2008-10-05 14:47   ` Sébastien Kunz-Jacques
2008-10-05 18:27     ` Ramiro Polla
2008-10-05 18:52       ` Sébastien Kunz-Jacques
2008-10-05 19:25         ` Ramiro Polla
2008-10-05 20:12           ` Sébastien Kunz-Jacques [this message]
2008-10-05 22:42             ` Ramiro Polla
2008-10-09 13:14               ` Ross Johnson
2008-10-09 19:51                 ` Sébastien Kunz-Jacques
2008-10-23  5:57                 ` Sébastien Kunz-Jacques

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=48E91F80.5080809@yahoo.fr \
    --to=kunzjacq@yahoo.fr \
    --cc=pthreads-win32@sourceware.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).