From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6607 invoked by alias); 7 Jul 2006 22:45:27 -0000 Received: (qmail 6511 invoked by uid 22791); 7 Jul 2006 22:45:26 -0000 X-Spam-Check-By: sourceware.org Received: from palrel11.hp.com (HELO palrel11.hp.com) (156.153.255.246) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Jul 2006 22:45:18 +0000 Received: from cacexg13.americas.cpqcorp.net (cacexg13.americas.cpqcorp.net [16.92.1.76]) by palrel11.hp.com (Postfix) with ESMTP id 0768A368E8; Fri, 7 Jul 2006 15:45:15 -0700 (PDT) Received: from cacexc12.americas.cpqcorp.net ([16.92.1.78]) by cacexg13.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 7 Jul 2006 15:45:15 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Solaris/X96 GC issues (was /bin/sh portability issues ...) Date: Fri, 07 Jul 2006 22:45:00 -0000 Message-ID: <65953E8166311641A685BDF71D865826BC296C@cacexc12.americas.cpqcorp.net> In-Reply-To: From: "Boehm, Hans" To: "Roger Sayle" , "Rainer Orth" Cc: , , Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2006-q3/txt/msg00086.txt.bz2 I checked Rainer's patch into the 7.0 tree, and added it to my current 6.8 tree. Thanks. That doesn't help with the Studio 11 cc problems that Rainer reported earlier. Someone with access to a suitable machine will have to track those down. The next step is to identify which objects are getting prematurely collected and why. It would be useful to see whether the offending list is referenced by an automatic or static pointer. In either case, it is also worth checking that GC_with_callee_saves_pushed ends up calling getcontext(), as it should. If it is a static pointer, and getcontext() is called correctly, I would next check that roots are being registered correctly, and the offending pointer is in a root segment. Setting the GC_DUMP_REGULARLY environment variable prints roots on a regular basis. It is possible that the studio 11 issue also affects gcc, but just happened to not be exercised. I think the GC_register_has_static_roots_callback issue was libjava-specific, since I hadn't gotten around to putting the patch that introduced it into the CVS tree. (I just corrected that). It should be defined in dyn_load.c, though it would be undefined if DYNAMIC_LOADING somehow didn't get defined in gcconfig.h. (That's probably not the way things should work. I made it a noop in that case for 7.0. But the real problem is probably in your gcconfig.h.) Slightly longer term, I'm not sure about the right path. I don't really have enough cycles to work on 7.0, so I don't expect to spend time on 6.8, except for relatively small and critical patches. If someone can generate a 6.8 patch to make Solaris/X86 work, I'm certainly fine with just putting it into gcc. I suspect it would be big enough to be problematic. Overall, my vote would be for 1) Making 7.0 work reliably on Solaris/X86. (I have been testing occasionally on Solaris/SPARC, and it seems OK there.) 2) Merging 7.0 into 4.3 early in that cycle. My expectation is that that would generate some breakage, mostly on less common platforms. But on platforms like Linux, I think 7.0 is actually now fairly stable. Hans > -----Original Message----- > From: java-patches-owner@gcc.gnu.org=20 > [mailto:java-patches-owner@gcc.gnu.org] On Behalf Of Roger Sayle > Sent: Friday, July 07, 2006 6:25 AM > To: Rainer Orth > Cc: java-patches@gcc.gnu.org; gcc-patches@gcc.gnu.org > Subject: Re: [JAVA] /bin/sh portability issues in=20 > scripts/check_jni_methods.sh >=20 >=20 > On 7 Jul 2006, Rainer Orth wrote: > > Roger Sayle writes: > > > terminating with a hard error, and enables libjava to reach the=20 > > > application linking steps at the end of the build (which=20 > suffer from=20 > > > boehmgc issues that I may not have resolved correctly). > > > > This is probably PR boehm-gc/21942. > > I've recently sent a new message about this to the boehm-gc list: > >=20 > http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2006-June/001334.h > > tml >=20 > Cool! Yes, this exactly the issue and your patch above is=20 > nearly identical to the one I have in my tree to allow the=20 > build to reach libjava. Unfortunately, I'm seeing a=20 > unresolved symbol reference to=20 > GC_register_has_static_roots_callback from libgcj.so when=20 > attempting to link jv-convert, so I wasn't sure if it was my=20 > X86_64/SUNOS5 changes in boehmgc/include/private/gcconfig.h=20 > that were at fault, or another latent problem in the libjava=20 > build system. >=20 > Anyway, thanks again for pointing out that you're on top of=20 > this particular issue (one less thing for me to worry about).=20 > Hopefully, Hans will comment soon. I did check the upstream=20 > sources to see if it was just an import of the latest boehmgc=20 > that was required. >=20 > Thanks again for addressing this. >=20 > Roger > -- >=20 >=20