Date: Mon, 22 Jul 1996 11:06:46 -0700 From: David Greenman <dg@root.com> To: Marc Slemko <marcs@valis.worldgate.com> Cc: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1411: vi dumps core when using 'set list' Message-ID: <199607221806.LAA00336@root.com> In-Reply-To: Your message of "Mon, 22 Jul 1996 11:04:22 MDT." <Pine.BSI.3.94.960722093222.21203B-100000@valis.worldgate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Mon, 22 Jul 1996, J Wunsch wrote: > >> As Marc Slemko wrote: >> >> > After further investigation, this problem appears to be the result of >> > using -m486 in the CFLAGS while compiling vi. If I compile without -m486, >> > it works fine. >> >> That's strange. Jordan already mentioned that 2.1.5 was not compiled >> with -m486, and i can add one more to this: everything i compile >> (including the tests to reproduce the behaviour of your PR) _has_ the >> -m486. > >Hmm. Well, I tried compiling it once again, this time with CFLAGS set to >"-O2 -m486 -pipe" and the problem was not there. Trying with "-O2 -m486", >the problem still wasn't there. With one of -O2 or -m486, it is still >there. Hey, I just tried -m486 again and it won't show up. Grr. Try >just using -O2 and see if you can make it show up. > >I just recompiled everything with "-O2"; the problem was there. I then >removed common/svi_line.o and did another make, this time with no special >CFLAGS. The problem went away. Removing common/svi_line.o once more and >doing a make with CFLAGS set to -O2 brought the problem back. ... >Since I do seem to be saying some conflicting things, if you still can't >reproduce it give me a week or so to at least straighten out my story and >see what else I can find. At this point, it is really looking like a gcc >bug. If it is a gcc bug, the next logical step would be to compare the >assembly output from gcc using various options; unfortunately, that's a >bit beyond what I am capable of understanding, especially since the >problem is in optimizations. There is a known bug with -O2. That's why we don't use it. The problem is with strength reduction. Try adding: -fno-strength-reduce and see if the bug goes away. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607221806.LAA00336>