Re: Low level folks: Beat this!

From: Jud McCranie (youknowwhat.mccranie_at_adelphia.net)
Date: 09/06/04


Date: Mon, 06 Sep 2004 00:03:49 -0400


>I got an integer overflow in your program with checks on. I hope that
>won't affect the results. Then I turned the checks off and
>optimization on.

BTW, your first and third algorithms gave incorrect results when I ran
them for 8 queens.

---
Replace you know what by j to email


Relevant Pages

  • Re: nconc and functional code
    ... Sorry, friend Pascal, your interpretation is incorrect. ... It doesn't conform with the ANS. ... optimization, and the general rules for optimization apply: Don't do it unless you're sure that it actually gains something - which you can only know for sure after profiling your program. ... While we usually call nconc as a slightly less consy version of append, the behavior of nconc on the last cons of a list is well defined by the ANS, and it is quite reasonable to call it with that side effect in mind. ...
    (comp.lang.lisp)
  • Re: How to find the datatype of a variable?
    ... I'd noticed the mlngDummy issue (even more obvious when running Command1_Click multiple times), but didn't worry about it because I figured it was irrelevant to the code with the overflow checks turned off...little did I know! ... Interestingly, this was only the case when remove integer overflow checking was checked; ... Fifth, the optimization "Remove Integer Overflow Checks" slowed it down quite a bit: ...
    (microsoft.public.vb.general.discussion)
  • Re: Where to include header files / A question of style?
    ... > The external guard macros preclude this optimization. ... No, that's incorrect. ... but it depends much on the headers ...
    (comp.lang.cpp)
  • Re: How to find the datatype of a variable?
    ... the first test came out noticeably slower than the ... Fifth, the optimization "Remove Integer Overflow ...
    (microsoft.public.vb.general.discussion)
  • RE: story about lost %ebx (stack corruption in inet_aton ?)
    ... and 8-CURRENT (i386 only, and only if optimization is enabled), but it ... seems to be incorrect. ... Most probably source is stack corruption in ... (should be built with -O1 or -O2 to expose that bug) ...
    (freebsd-current)