This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Normalizing the bitmap APIs.

From: Diego Novillo <dnovillo at google dot com>
To: Lawrence Crowl <crowl at googlers dot com>
Cc: Richard Biener <richard dot guenther at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Thu, 11 Oct 2012 15:16:12 -0400
Subject: Re: Normalizing the bitmap APIs.
References: <CAGqM8fbx+NtogY08ziCWv8v0fAcFLmAyDMH_VT=XHLq2Fz2nXA@mail.gmail.com> <CAFiYyc3dcb=GbTPW-KT-7_vFaM6yue1e+y2R4M0z_bFNUDc+tA@mail.gmail.com> <CAGqM8fbRYtZOSAS8OiH=6p__x52=kEzXKH3SK1ZcNvsB5xgCWw@mail.gmail.com>

On 2012-10-11 13:26 , Lawrence Crowl wrote:

My only other concern was that the mapping between those function
names and the tasks to be done sometimes seemed less than obvious.
So, I proposed the name change.  However, I think the current names
are workable, assuming an acceptable solution to the above problem.

I would say, add both variants and make the empty ones drop the return value. So, for instance, bitmap_ior returns a value, so make bitmap_ior_cg drop it.

Diego.

Follow-Ups:
- Re: Normalizing the bitmap APIs.
  - From: Lawrence Crowl

References:
- Normalizing the bitmap APIs.
  - From: Lawrence Crowl
- Re: Normalizing the bitmap APIs.
  - From: Richard Biener
- Re: Normalizing the bitmap APIs.
  - From: Lawrence Crowl

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