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: darwin bootstrap failure in mainline

From: Richard Henderson <rth at redhat dot com>
To: Dale Johannesen <dalej at apple dot com>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, gcc List <gcc at gcc dot gnu dot org>, Fariborz Jahanian <fjahanian at apple dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 18 Aug 2004 11:48:40 -0700
Subject: Re: darwin bootstrap failure in mainline
References: <470B07B5-F137-11D8-B9A9-000A95BA54A6@apple.com> <20F57D1B-F139-11D8-950D-00039351ED8A@physics.uc.edu> <4635B64E-F13D-11D8-8E24-000A95D7CD40@apple.com>

On Wed, Aug 18, 2004 at 10:37:28AM -0700, Dale Johannesen wrote:
> No, it wasn't wrong, RTX_UNCHANGING_P was defined to be valid on 
> registers, and I'll be surprised if Darwin was the only port doing that.

It wasn't the only port.  Most of the other ocurrences were obvious.
This case confused my eye to believe that we were always talking 
about a memory.

Thanks to Andrew for fixing it up.

r~

References:
- darwin bootstrap failure in mainline
  - From: Fariborz Jahanian
- Re: darwin bootstrap failure in mainline
  - From: Andrew Pinski
- Re: darwin bootstrap failure in mainline
  - From: Dale Johannesen

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