This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH v5] Make bindresvport() function to multithread-safe

From: Peng Haitao <penght at cn dot fujitsu dot com>
To: Andreas Schwab <schwab at linux-m68k dot org>
Cc: libc-alpha at sourceware dot org, "H.J. Lu" <hjl dot tools at gmail dot com>
Date: Tue, 16 Oct 2012 18:08:21 +0800
Subject: Re: [PATCH v5] Make bindresvport() function to multithread-safe
References: <1350378414-11341-1-git-send-email-penght@cn.fujitsu.com> <m2bog2pycz.fsf@igel.home> <507D2DA5.3010609@cn.fujitsu.com> <m27gqqpwh1.fsf@igel.home>

On 10/16/2012 06:00 PM, Andreas Schwab wrote:
> Peng Haitao <penght@cn.fujitsu.com> writes:
> 
>> First, Carlos O'Donell suggestion define a macro.
>> http://sourceware.org/ml/libc-alpha/2012-09/msg00590.html
> 
> He didn't mean it literally.
> 
>> Second, your suggestion is different with H.J. Lu:(
>> http://sourceware.org/ml/libc-alpha/2012-09/msg00762.html
> 
> A macro still means inlining it, only worse.
> 

Yeah:(

Modify macro to function not inlining, is OK?

-- 
Best Regards,
Peng

References:
- [PATCH v5] Make bindresvport() function to multithread-safe
  - From: Peng Haitao
- Re: [PATCH v5] Make bindresvport() function to multithread-safe
  - From: Andreas Schwab
- Re: [PATCH v5] Make bindresvport() function to multithread-safe
  - From: Peng Haitao
- Re: [PATCH v5] Make bindresvport() function to multithread-safe
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]