Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 14486 invoked from network); 25 May 2007 02:58:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 May 2007 02:58:49 -0000 Received: (qmail 54678 invoked by uid 500); 25 May 2007 02:58:52 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 54656 invoked by uid 500); 25 May 2007 02:58:52 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 54647 invoked by uid 99); 25 May 2007 02:58:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2007 19:58:52 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nbeyer@gmail.com designates 64.233.162.239 as permitted sender) Received: from [64.233.162.239] (HELO nz-out-0506.google.com) (64.233.162.239) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2007 19:58:46 -0700 Received: by nz-out-0506.google.com with SMTP id i1so737067nzh for ; Thu, 24 May 2007 19:58:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=beFwBIw3jI1K2TagHZHDpQM/jak24RjHga+RZisei6lv9xhtGlJgDQKQ7MeRmHgH/LbpGJd/20ysGOBke7l82ISipsPRx9KDP0SNM+ZpnitzQvjY0D00sqfksKBRNXrFQS1GTFOX6S2X9oSGARU/GsClePC3Qa0NiWZAcG2Nyws= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Aa/Z0TzkM+lh1KpFOK7iyDFN7S5xaHm+TPeoCw8CxnLii5tdjGOqf81RstD7UKhiYktN0FB3fEx9458Ujaul23v8wmwo2SaGi7hcZ1KEwL8xeonSW2rSPdp0wbQ/agtfN9Ycbxvp1XeAUxdSRppl7k5WMCWcpyAe7TeenKC4OeM= Received: by 10.114.13.1 with SMTP id 1mr1239159wam.1180061904881; Thu, 24 May 2007 19:58:24 -0700 (PDT) Received: by 10.114.195.5 with HTTP; Thu, 24 May 2007 19:58:24 -0700 (PDT) Message-ID: <3b3f27c60705241958l5d1835b9l6b401b54cefa63c1@mail.gmail.com> Date: Thu, 24 May 2007 21:58:24 -0500 From: "Nathan Beyer" Sender: nbeyer@gmail.com To: dev@harmony.apache.org Subject: Re: problem under windows In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070522151222.B67E.MMM@projectumbra.org> <20070523003314.B683.MMM@projectumbra.org> X-Google-Sender-Auth: 9bcd4d85fa8a6340 X-Virus-Checked: Checked by ClamAV on apache.org BTW - I do have P3 machines for testing. One's running W2K and the other's running Ubuntu. -Nathan On 5/24/07, Elford, Chris L wrote: > FYI, I have created http://issues.apache.org/jira/browse/HARMONY-3961 > To reflect this desired behavior. > > Regards, > Chris Elford > Intel SSG/Enterprise Solutions Software Division > > -----Original Message----- > From: Elford, Chris L [mailto:chris.l.elford@intel.com] > Sent: Thursday, May 24, 2007 9:46 AM > To: dev@harmony.apache.org > Subject: RE: problem under windows > > Interesting. Its good to hear that some thought has been given to P3 > class systems. I would think /arch:SSE would be okay. This would let > us run on both P3s and Athlon (like the one that Michael was trying to > run on) which support both MMX and SSE but not SSE2. > > Is there a compiler option that generates back-off MMX code on platforms > that don't support SSE or SSE2 instructions? If so, it would result in > larger executables and might impact code locality but it might be a good > tradeoff. > > Regards, > > Chris Elford > Intel SSG/Enterprise Solutions Software Division > > -----Original Message----- > From: Mikhail Fursov [mailto:mike.fursov@gmail.com] > Sent: Thursday, May 24, 2007 2:12 AM > To: dev@harmony.apache.org > Subject: Re: problem under windows > > Well, it looks like we need to remove this line from jitrino.dll build > configuration for 32bit platform. > > > On 5/24/07, Mikhail Fursov wrote: > > > > On 5/24/07, Elford, Chris L wrote: > > > > > > Hi all, > > > > > > I tracked down a system that has SSE but not SSE2 (a dual > processor P3 > > > system). For me, adding "-xe ii" to the ntsd command line let the > > > debugger break in at the first chance exception. It reports that > what I > > > > > > believe is an SSE2 instruction does indeed happen during jitrino.dll > > > startup. > > > > > > 01365fb0 f20f100520553901 movsd xmm0,qword ptr > > > [jitrino!JIT_gc_start+0xd5810 (01395520)] > > > > > > Without jitrino symbol information ( e.g., a pdb file for > jitrino.dll), > > > its hard to tell what function is being executed (it is unlikely > that it > > > is JIT_gc_start. It would be nice if the snapshot builds included > > > symbol files to help make for more meaningful stack traces. > > > > > > It may be good to discuss [again?] on the lists whether more people > can > > > come into the project to help create legacy modes that earlier > > > instruction sets (and earlier Oses) can still execute without > crippling > > > current instruction set processors (and/or OSes). > > > > > > I don't see an open JIRA about this one. The closest I see is > > > http://issues.apache.org/jira/browse/HARMONY-3246 which is more > about > > > code that the JIT creates rather than the JIT itself. > > > > > > Ntsd log below showing more detail around faulting instruction. > > > Mikhail? > > > > > > You're right that we fixed Jitrino.OPT to generate SSE independent > code > > (use x87) if SSE2 is not available. > > Another JIRA (not commited yet): > http://issues.apache.org/jira/browse/HARMONY-3737 > > makes JET to compile all methods without FPU insts (>90% of methods) > and > > pass other methods to OPT > > I checked dumpbin /disasm for jitrino.dll and see a lot of SSE/SSE2 > insts > > in code. > > > > It's possible that our compiler options for jitrino.dll are too > > aggressive. I will check it and report. > > > > -- > > Mikhail Fursov > > > > > -- > Mikhail Fursov >