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] New -fstack-check implementation

From: Duncan Sands <duncan dot sands at math dot u-psud dot fr>
To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
Cc: ebotcazou at adacore dot com, gcc-patches at gcc dot gnu dot org
Date: Sun, 30 Mar 2008 15:32:22 +0200
Subject: Re: [PATCH] New -fstack-check implementation
References: <200803292314.24014.ebotcazou@adacore.com> <200803301511.41131.duncan.sands@math.u-psud.fr> <10803301320.AA09881@vlsi1.ultra.nyu.edu>

On Sunday 30 March 2008 15:20:43 Richard Kenner wrote:
> > in the past valgrind has noticed invalid memory accesses when using
> > -fstack-check in a multi-tasking program for example when a task exits
> > (the invalid accesses coming from the stack checking code).  Is this a
> > known (fixed) problem?  If not, I will try to cook up a testcase.
> 
> By definition, stack checking using any probing mechanism will generate
> "invalid" accesses.

Except in this case valgrind never complained about the stack checking
code generated by -fstack-check.

Duncan.

References:
- [PATCH] New -fstack-check implementation
  - From: Eric Botcazou
- Re: [PATCH] New -fstack-check implementation
  - From: Duncan Sands
- Re: [PATCH] New -fstack-check implementation
  - From: Richard Kenner

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