Christian Weisgerber mips.inka.de> writes:
> Except that OpenBSD's gcc does not enable -fstrict-aliasing with -O2.
> See gcc-local(1).
The diagnosis may be incorrect, but the medication still works.
James Wright <[EMAIL PROTECTED]> wrote:
>o You must not try to compile epic with "gcc -O2" because -O2 will
> generate bad code that leads to random crashes. When you use -O2,
> gcc assumes the source is conformant to ISO C99's requirements about
> alias-safety, and EPIC, b
James,
I compiled epic5 with default options and it uses -O:
alemao:7$ make
gcc -g -O -I/usr/local/include -I./../include -I../include -c alias.c
gcc -g -O -I/usr/local/include -I./../include -I../include -c alist.c
gcc -g -O -I/usr/local/include -I./../include -I../include -c array.c
gcc -g -
guilherme m. schroeder wrote:
James,
I got in this problem too on amd64. Sometimes when you resize the
screen, epic crashes and stops responding. After that, 100% of the cpu
is used by the program. Sometimes when you paste some data insider it
using the mouse it crashes too. I'll try this patch
James,
I got in this problem too on amd64. Sometimes when you resize the
screen, epic crashes and stops responding. After that, 100% of the cpu
is used by the program. Sometimes when you paste some data insider it
using the mouse it crashes too. I'll try this patch to see what
happens here.
BTW,
this probably needs testing on alpha/mips64, it may be safer to
use -O0.
On 2008/10/13 13:25, James Wright wrote:
> -current of ~ Oct 5th, epic4-2.10 (both package and built from ports),
> hangs on inputting ^C. Thanks to the helpful folks of #epic, I was
> pointed to this on the epic website (th
-current of ~ Oct 5th, epic4-2.10 (both package and built from ports),
hangs on inputting ^C. Thanks to the helpful folks of #epic, I was
pointed to this on the epic website (though they should add it to the
INSTALL notes for EPIC4, not just EPIC5
http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/INST
-current of ~ Oct 5th, epic4-2.10 (both package and built from ports),
hangs on inputting ^C. Thanks to the helpful folks of #epic, I was
pointed to this on the epic website (though they should add it to the
INSTALL notes for EPIC4, not just EPIC5
http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/I
