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][RFA] Fix -fstack-check with really big frames on aarch64

On Thu, Jun 22, 2017 at 08:42:54PM +0200, Richard Biener wrote:
> >The thought of scanning the assembly code or RTL is too painful to
> >contemplate.  THus I've been pondering having the prologue expanders
> >emit notes into the dump file about what they did and why WRT probing.
> >
> >Or maybe we should use the unit testing framewhere here.  Hmmm....
> 
> I've been thinking that for Linux the kernel should have a way (/proc/pid controlled) to only extend the stack mapping for faults to the page exactly below the current end of the mapping.  So we'd get a segfault for any missed probe.
> 
> Just for QA purposes of course, I expect too many false positives in a full system.

Or valgrind could have such a tool or option.

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