This is the mail archive of the gcc-patches@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: RFA: MN10300: Include saved registers in stack usage

From: Jeff Law <law at redhat dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: Nick Clifton <nickc at redhat dot com>, aoliva at redhat dot com, gcc-patches at gcc dot gnu dot org
Date: Wed, 05 Feb 2014 14:55:49 -0700
Subject: Re: RFA: MN10300: Include saved registers in stack usage
Authentication-results: sourceware.org; auth=none
References: <87fvnx4z57 dot fsf at redhat dot com> <52F27362 dot 60303 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1402051815240 dot 7511 at digraph dot polyomino dot org dot uk>

On 02/05/14 11:26, Joseph S. Myers wrote:

On Wed, 5 Feb 2014, Jeff Law wrote:

However, it's pretty easy to avoid the headaches and just provide a popcount
routine.   I don't think this code is at all performance critical (once per
function being compiled), so a simple popcount should be sufficient.  No need
for lookup tables IMHO.


hwint.[ch] provide popcount_hwi, if HOST_WIDE_INT is a suitable type.

Even better.


(Personally I think there are lots of bits of standard integer
manipulation functionality, such as popcount, that are common in processor
instructions and compiler intrinsics, but could do with having bindings in
ISO C to provide a standard way to access that functionality.

Agreed.


Jeff

References:
- RFA: MN10300: Include saved registers in stack usage
  - From: Nick Clifton
- Re: RFA: MN10300: Include saved registers in stack usage
  - From: Jeff Law
- Re: RFA: MN10300: Include saved registers in stack usage
  - From: Joseph S. Myers

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