Re: [PATCH] 1.8.3 p1 segfault in array.c- bccwin32 - bcc5.5 (free) compiler bug

Hi.

>I'll let Ocean, or someone else, decide on that when they've noticed
>the speed increase after removing their overheads.

Umm, this is difficult to answer...

Honestly, I want Borland to fix this. I found bug tracking system on their site,
so I think this is the place for letting them know the problem.
(http://qc.borland.com/wc/qcmain.aspx)

But probably they won't fix this.... because another two years old inline bug report
is still unfixed. http://qc.borland.com/wc/qcmain.aspx?d=4784

Anyway, we did some workaround already, so there is no reason not to do another
workaround.

  http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/parse.y.diff?r1=1.365;r2=1.366

This is needed because ...

  #include <stdio.h>

  #pragma option -Od /* in ruby code, this is not needed */

  struct hoge
  {
      unsigned __int64 value; /* must be in struct */
  };

  int main()
  {
      struct hoge a;

      struct hoge *p = &a; /* access through the pointer */

      p->value >>= 1; /* SEGV */ /* won't SEGV if p->value = p->value >> 1 */

      return 0;
  }

But I don't like workaround, even on above bug, I propsed not to use __int64 totally.
So I want to recommend not to use inline.

  make OPTFLAGS="-v- -vi- -O2"

# bcc32 port maintainer KONISHI Hiromasa might have a different thought.