Hi,
I recently ran into a case, where x86 fails to run correctly.
Checking into the emitted code, it seems that the local memory anchored at
ebp has conflict with stack memory anchored at esp prepared for function
calls.
For example, let us say:
foo()
{
...
call bar();
}
There is some local data for foo() at ebp-170h. while preparing the call
to bar, some data is written to esp+17h. The problem is that esp+17h and
ebp-170h point to the same address, and therefore the data is corrupted.
Has anyone seen this problem before? and is there any fix or work around
for that?
Thanks!
-Peng
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130130/bc15b08f/attachment.html>
On Wed, Jan 30, 2013 at 11:27:04AM -0500, Peng Cheng wrote:> Checking into the emitted code, it seems that the local memory anchored at > ebp has conflict with stack memory anchored at esp prepared for function > calls.Can you provide real code? Joerg
> Has anyone seen this problem before? and is there any fix or work around > for that?Please provide a testcase and fill LLVM problem report into bugzilla. Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
Bug is reported with test cases. see http://llvm.org/bugs/show_bug.cgi?id=15124 . Thanks, -Peng On Wed, Jan 30, 2013 at 12:14 PM, Anton Korobeynikov < anton at korobeynikov.info> wrote:> > Has anyone seen this problem before? and is there any fix or work around > > for that? > Please provide a testcase and fill LLVM problem report into bugzilla. > > Thanks! > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130130/e4e2cf1f/attachment.html>