public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Loeser (halcy0n)" <halcy0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-libs/zthread/files: zthread-2.3.2-no-fpermissive.diff
Date: Sun, 19 Apr 2009 20:00:35 +0000	[thread overview]
Message-ID: <E1LvdBr-0008Lu-DQ@stork.gentoo.org> (raw)

halcy0n     09/04/19 20:00:35

  Added:                zthread-2.3.2-no-fpermissive.diff
  Log:
  Patch so that -fpermissive is not needed to build.  Thanks to Wilfried Holzke <gentoo AT holzke DOT net>; bug #232645
  (Portage version: 2.2_rc30/cvs/Linux x86_64)

Revision  Changes    Path
1.1                  dev-libs/zthread/files/zthread-2.3.2-no-fpermissive.diff

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/zthread/files/zthread-2.3.2-no-fpermissive.diff?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/zthread/files/zthread-2.3.2-no-fpermissive.diff?rev=1.1&content-type=text/plain

Index: zthread-2.3.2-no-fpermissive.diff
===================================================================
--- include/zthread/Guard.h.orig	2008-07-22 14:46:28.000000000 +0200
+++ include/zthread/Guard.h	2008-07-22 14:51:41.000000000 +0200
@@ -491,7 +491,7 @@
     
   try {
     
-    if(!isDisabled())
+    if(!LockHolder<LockType>::isDisabled())
       LockingPolicy::destroyScope(*this);
     
   } catch (...) { /* ignore */ }  
--- src/MutexImpl.h.orig	2008-07-22 14:54:40.000000000 +0200
+++ src/MutexImpl.h	2008-07-22 15:03:30.000000000 +0200
@@ -153,7 +153,7 @@
 
       _owner = self;
 
-      ownerAcquired(self);
+      MutexImpl<List,Behavior>::ownerAcquired(self);
       
     }
 
@@ -164,7 +164,7 @@
       _waiters.insert(self);
       m.acquire();
 
-      waiterArrived(self);
+      MutexImpl<List, Behavior>::waiterArrived(self);
 
       {        
       
@@ -173,7 +173,7 @@
       
       }
 
-      waiterDeparted(self);
+      MutexImpl<List, Behavior>::waiterDeparted(self);
 
       m.release();
         
@@ -192,7 +192,7 @@
           assert(_owner == 0);
           _owner = self;    
 
-          ownerAcquired(self);
+          MutexImpl<List, Behavior>::ownerAcquired(self);
 
           break;
         
@@ -236,7 +236,7 @@
 
       _owner = self;
 
-      ownerAcquired(self);
+      MutexImpl<List, Behavior>::ownerAcquired(self);
       
     }
 
@@ -253,7 +253,7 @@
       
         m.acquire();
 
-        waiterArrived(self);
+        MutexImpl<List, Behavior>:: waiterArrived(self);
       
         {
         
@@ -262,7 +262,7 @@
         
         }
 
-        waiterDeparted(self);
+	MutexImpl<List, Behavior>::waiterDeparted(self);
       
         m.release();
         
@@ -284,7 +284,7 @@
           assert(0 == _owner);
           _owner = self;
 
-          ownerAcquired(self);
+	MutexImpl<List, Behavior>::ownerAcquired(self);
         
           break;
         
@@ -326,7 +326,7 @@
 
     _owner = 0;
 
-    ownerReleased(impl);
+    MutexImpl<List, Behavior>::ownerReleased(impl);
   
     // Try to find a waiter with a backoff & retry scheme
     for(;;) {






                 reply	other threads:[~2009-04-19 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1LvdBr-0008Lu-DQ@stork.gentoo.org \
    --to=halcy0n@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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