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: Split Stacks proposal


John Regehr <regehr@cs.utah.edu> writes:

> This effort is relevant:
>
> http://research.microsoft.com/en-us/um/people/jcondit/capriccio-sosp-2003.pdf

Yes.  Unfortunately, their analysis which lets them avoid testing at the
entry to each function requires a complete call graph, which is not
something gcc can assume in practice.  Even when using LTO a genuinely
complete call graph is not the normal case.

It's true that we can use an analysis along these lines to avoid some
checks in file-static functions (or, with LTO, in functions which get
hidden visibility for whatever reason).  However, I suspect that in
practice this will be a minor optimization--worth doing, but only when
everything else is working.

Ian


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