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: resolve libstdc++/5198

From: Roman Zippel <zippel at linux-m68k dot org>
To: Richard Henderson <rth at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Thu, 24 Jan 2002 23:45:07 +0100
Subject: Re: resolve libstdc++/5198
References: <20020123174001.A994@redhat.com> <3C505A75.6060102@linux-m68k.org> <20020124131159.B10485@redhat.com>

Hi,

Richard Henderson wrote:

> Anyway, m68k is freaky in saving so much state on faults, I didn't
> know if it would save intermediate results when faulting in the
> middle of an indirect memory thing.

Hmm, it does save pending writes on the stack, and the fault handler can
be interrupted by another process, so using cas is indeed safer.

bye, Roman

References:
- resolve libstdc++/5198
  - From: Richard Henderson
- Re: resolve libstdc++/5198
  - From: Roman Zippel
- Re: resolve libstdc++/5198
  - From: Richard Henderson

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