| Subject: | Re: How could pthread_mutex_lock/unlock affect compiler optimization and / or caching?? |
|---|---|
| From: | Paul Pluzhnikov <ppluzhnikov-nsp@xxxxxxxxx> |
| Date: | Thu, 17 Jul 2008 07:15:57 -0700 |
| Newsgroups: | gnu.gcc.help |
mynickmynick <mynickmynick@xxxxxxxxx> writes: > How could pthread_mutex_lock / unlock affect compiler optimization > and / or caching?? Homework? A: In many ways. Think about it: can a variable be kept in a register across a call to pthread_mutex_lock() ? Cheers, -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | How could pthread_mutex_lock/unlock affect compiler optimization and / or caching??, mynickmynick |
|---|---|
| Next by Date: | Re: How could pthread_mutex_lock/unlock affect compiler optimization and / or caching??, mynickmynick |
| Previous by Thread: | How could pthread_mutex_lock/unlock affect compiler optimization and / or caching??, mynickmynick |
| Next by Thread: | Re: How could pthread_mutex_lock/unlock affect compiler optimization and / or caching??, mynickmynick |
| Indexes: | [Date] [Thread] [Top] [All Lists] |