Received: by 10.58.180.134 with SMTP id do6mr5352475vec.5.1349187136509;
        Tue, 02 Oct 2012 07:12:16 -0700 (PDT)
X-BeenThere: v8-dev@googlegroups.com
Received: by 10.52.89.80 with SMTP id bm16ls269213vdb.9.gmail; Tue, 02 Oct
 2012 07:12:15 -0700 (PDT)
Received: by 10.52.174.201 with SMTP id bu9mr4655997vdc.5.1349187135421;
        Tue, 02 Oct 2012 07:12:15 -0700 (PDT)
Received: by 10.52.174.201 with SMTP id bu9mr4655996vdc.5.1349187135412;
        Tue, 02 Oct 2012 07:12:15 -0700 (PDT)
Return-Path: <3P_ZqUBAKBmAAMBCQGRC-LMPCNJWEMMEJC.AMKTg-BCTEMMEJCEPMSNQ....@codesite.bounces.google.com>
Received: from mail-vc0-f204.google.com (mail-vc0-f204.google.com [209.85.220.204])
        by gmr-mx.google.com with ESMTPS id bn19si57645vdb.0.2012.10.02.07.12.15
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 02 Oct 2012 07:12:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3P_ZqUBAKBmAAMBCQGRC-LMPCNJWEMMEJC.AMKTg-BCTEMMEJCEPMSNQ....@codesite.bounces.google.com designates 209.85.220.204 as permitted sender) client-ip=209.85.220.204;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3P_ZqUBAKBmAAMBCQGRC-LMPCNJWEMMEJC.AMKTg-BCTEMMEJCEPMSNQ....@codesite.bounces.google.com designates 209.85.220.204 as permitted sender) smtp.mail=3P_ZqUBAKBmAAMBCQGRC-LMPCNJWEMMEJC.AMKTg-BCTEMMEJCEPMSNQ....@codesite.bounces.google.com; dkim=pass header...@google.com
Received: by vcbfl13 with SMTP id fl13so2059924vcb.3
        for <v8-dev@googlegroups.com>; Tue, 02 Oct 2012 07:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:reply-to:x-generated-by:x-googlecode-project
         :x-googlecode-issue-id:message-id:date:subject:from:to:content-type;
        bh=n7Py2FOFg/CpSpT5/qGPtWeHBgd1KJDg1mit8K1wSH4=;
        b=UahzPli/YkMuzD+ADx3kQWOsy8qFSSgJpbu+q4iqP1BSUrTiP2zRhFri6CKy29Ky4G
         tikYKaH8vjZ4voT0bLYf3vUTWWIB0e//rp5odVhxuogNHxNsUPbMqrvWfo9T5nPQgWgM
         /6g3lxib8Ms2tFLxCeheXx9mhhGrFQpPbl34HwswTm6Dwegn+maMZ2MP+oj/KKJiEDEm
         OqhPE4fEd4E175U+AOQVpFiDILG/wWQv+laCGBesGt7MkfWje2JmfW9IwxMolcF6LS/I
         4n2ETOSBoWlpYFnWf0rfg3fZ8WaDc8b1OeCdIVHOPv37mbBGRZD0dil/TdWBAx6OsWUL
         bLvQ==
MIME-Version: 1.0
Received: by 10.224.189.75 with SMTP id dd11mr1107757qab.6.1349187135221; Tue,
 02 Oct 2012 07:12:15 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: v8
X-GoogleCode-Issue-Id: 2354
Message-ID: <0-11690816309429728379-3673556134912972444-codesite-noreply=google....@googlecode.com>
Date: Tue, 02 Oct 2012 14:12:15 +0000
Subject: Issue 2354 in v8: ARM: Crypto not completing since r12646
From: codesite-nore...@google.com
To: v8-dev@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Status: New
Owner: ----

New issue 2354 by martyn.c...@arm.com: ARM: Crypto not completing since  
r12646
http://code.google.com/p/v8/issues/detail?id=2354

Since SVN revision 12646, the V8 Crypto benchmark no longer completes, or  
takes a very long time to complete, on ARM Cortex-A8 and A9.