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: fold_builtin_memcpy cannot optimize <retval>?

From: Paul Brook <paul at codesourcery dot com>
To: gcc at gcc dot gnu dot org
Cc: Mark Mitchell <mark at codesourcery dot com>,law at redhat dot com,Jakub Jelinek <jakub at redhat dot com>,Richard Guenther <rguenth at tat dot physik dot uni-tuebingen dot de>
Date: Fri, 21 Jan 2005 18:23:08 +0000
Subject: Re: fold_builtin_memcpy cannot optimize <retval>?
Organization: CodeSourcery
References: <Pine.LNX.4.44.0501211136170.16464-100000@alwazn.tat.physik.uni-tuebingen.de> <1106330271.30575.265.camel@localhost.localdomain> <41F14409.8000200@codesourcery.com>

On Friday 21 January 2005 18:03, Mark Mitchell wrote:
> Jeffrey A Law wrote:
> > I'm not an expert on the differences in the semantics of POINTER_TYPE
> > and REFERENCE_TYPE, but I do know that I've been treating them as
> > effectively the same.
>
> The only difference is that a REFERENCE_TYPE object can never be NULL.

Didn't we discuss this before and decide that REFERENCE_TYPE objects can be 
NULL?
http://gcc.gnu.org/ml/gcc-patches/2004-08/msg01463.html

Paul

Follow-Ups:
- Re: fold_builtin_memcpy cannot optimize <retval>?
  - From: Mark Mitchell

References:
- fold_builtin_memcpy cannot optimize <retval>?
  - From: Richard Guenther
- Re: fold_builtin_memcpy cannot optimize <retval>?
  - From: Jeffrey A Law
- Re: fold_builtin_memcpy cannot optimize <retval>?
  - From: Mark Mitchell

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