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: [PATCH 1/6] Thread pointer built-in functions, core parts

From: Mike Stump <mikestump at comcast dot net>
To: Chung-Lin Tang <cltang at codesourcery dot com>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, Richard Sandiford <rdsandiford at googlemail dot com>
Date: Fri, 13 Jul 2012 18:58:19 -0700
Subject: Re: [PATCH 1/6] Thread pointer built-in functions, core parts
References: <4FFE741E.7080506@codesourcery.com> <08E650FE-14AA-4348-9C5C-FCD2F91307F0@comcast.net> <4FFFC489.5030704@codesourcery.com>

On Jul 12, 2012, at 11:47 PM, Chung-Lin Tang <cltang@codesourcery.com> wrote:
>> and then for the return value, maybe a const0_rtx for Pmode.
> 
> A little unsure what you mean.  Are you referring to return const0_rtx
> for default_expand_builtin_thread_pointer() instead of NULL?

Yes.  NULL has the habit of crashing things if they don't expect it.

Follow-Ups:
- Re: [PATCH 1/6] Thread pointer built-in functions, core parts
  - From: Chung-Lin Tang

References:
- [PATCH 1/6] Thread pointer built-in functions, core parts
  - From: Chung-Lin Tang
- Re: [PATCH 1/6] Thread pointer built-in functions, core parts
  - From: Mike Stump
- Re: [PATCH 1/6] Thread pointer built-in functions, core parts
  - From: Chung-Lin Tang

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