<div class="gmail_quote">On Mon, Jan 2, 2012 at 17:45, Reza Madankan <span dir="ltr"><<a href="mailto:rm93@buffalo.edu">rm93@buffalo.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, the matrix is dense. So, you mean that there is no way to evaluate the matrix, exactly?</blockquote><div><br></div><div>You can evaluate it, but there is almost always a way to get the "science" result without computing all the entries. Such an algorithm would be faster.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> .... I have run the code for smaller size of Ypcq and it's working. But for larger sizes I get the error that I mentioned.</blockquote>
</div><br><div>It's possible that the corruption is caused by some integer overflow and not from actually running out of memory, but it's definitely worth checking that smaller sizes do not have some small error that is detectable by Valgrind (e.g. an uninitialized variable that happens to be equal to 0 at small sizes, or an off-by-one error that does not cause problems for small sizes).</div>