Related articles |
---|
stack overflow at compile time jatin.bhateja@conexant.com (Jatin Bhateja) (2006-04-27) |
Re: stack overflow at compile time NOSPAMrszeflerNOSPAM@murator.com.pl (RobertSzefler) (2006-04-27) |
Re: stack overflow at compile time vb@compilers.de (Volker Barthelmann) (2006-04-27) |
Re: stack overflow at compile time nitin@CoWare.com (Nitin Gupta) (2006-04-27) |
Re: stack overflow at compile time henry@spsystems.net (2006-04-27) |
Re: stack overflow at compile time gah@ugcs.caltech.edu (glen herrmannsfeldt) (2006-04-28) |
Re: stack overflow at compile time jvorbrueggen@mediasec.de (=?ISO-8859-1?Q?Jan_Vorbr=FCggen?=) (2006-04-28) |
Re: stack overflow at compile time jatin.bhateja@conexant.com (Jatin Bhateja) (2006-04-28) |
[7 later articles] |
From: | RobertSzefler <NOSPAMrszeflerNOSPAM@murator.com.pl> |
Newsgroups: | comp.compilers |
Date: | 27 Apr 2006 23:32:26 -0400 |
Organization: | Internet Partners |
References: | 06-04-157 |
Keywords: | storage, analysis |
Posted-Date: | 27 Apr 2006 23:32:26 EDT |
Jatin Bhateja wrote:
> Hi,
>
> Is it possible at compile time to know whether there is a possibility of
> stack overflow at run time? I feel that to some extent it is possible.
This is obviously equivalent to deciding halting, which of course cannot
be done in general. But see for example
http://www.cs.utah.edu/flux/papers/emsoft03/
and references therein. The topic is presented from embedded device
perspective there - that might be of specific interest to you.
Interestingly, there is quite a big body of research (of sometimes
questionable quality for sure) on this topic. I don't have the
references at hand, but remember reading several papers from major
conferences on this - anyone?
Return to the
comp.compilers page.
Search the
comp.compilers archives again.