Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Aug 2002 19:40:03 -0700 (PDT)
From:      Jay Sachs <jay@eziba.com>
To:        freebsd-ports@FreeBSD.org
Subject:   Re: ports/41961: jikes 1.16 core dumps on FreeBSD (but not on RedHat Linux 7.3)
Message-ID:  <200208260240.g7Q2e3fd027422@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/41961; it has been noted by GNATS.

From: Jay Sachs <jay@eziba.com>
To: freebsd-gnats-submit@FreeBSD.org, archie@FreeBSD.org
Cc:  
Subject: Re: ports/41961: jikes 1.16 core dumps on FreeBSD (but not on RedHat
 Linux 7.3)
Date: Sun, 25 Aug 2002 22:40:37 -0400

 Freshly -supped ports tree, and -stable as of Aug 7.
 
 Attempt 1: I build the port with no optimization and debugging
 on, as follows:
 
    make CXXFLAGS='-g -pipe'
 
 No core dump, just a (jikes) warning about use of '$' in an identifier.
 
 So apparently the optimization in the 4.6-stable c++ compiler is
 a bit flakey.
 
 Attempt 2: Turn on optimization, building jikes as follows:
    make CXXFLAGS='-g -O -pipe'
 
 Ok, got core dump. Ran gdb, and the stack was filled
 with near-endless repetition of the frame pair
 
 #177 0x82071d2 in Semantic::ProcessBinaryExpression (this=0x8d18000,
      expr=0x8d1e474) at expr.cpp:6640
 #178 0x81f30c8 in Semantic::ProcessPLUS (this=0x8d18000, expr=0x8d1e4c0)
      at semantic.h:1398
 
 883 frames in total. So it looks like the optimizer inserted an infinite
 loop. It looks like the gcc 2.95.4 import of June 20 could be the
 culprit. The RELENG_4_6 branches (4.6-RELEASE, 4.6.1, 4.6.2 etc)
 do NOT have 2.95.4 imported, so if someone could test one of those
 systems we could pretty much nail down that it's a 2.95.4 optimizer bug.
 
 jay
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208260240.g7Q2e3fd027422>