Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion ARM: Add literal pool blocking to position critical code. (issue 10451037)

Received: by 10.101.136.25 with SMTP id o25mr2878864ann.8.1339507787068;
        Tue, 12 Jun 2012 06:29:47 -0700 (PDT)
X-BeenThere: v8-dev@googlegroups.com
Received: by 10.236.121.34 with SMTP id q22ls3329255yhh.7.gmail; Tue, 12 Jun
 2012 06:29:46 -0700 (PDT)
Received: by 10.100.246.30 with SMTP id t30mr10564985anh.17.1339507786364;
        Tue, 12 Jun 2012 06:29:46 -0700 (PDT)
Received: by 10.100.246.30 with SMTP id t30mr10564983anh.17.1339507786349;
        Tue, 12 Jun 2012 06:29:46 -0700 (PDT)
Return-Path: <3SkTXTxUJALMVakhfbnfVhWXkXobXp-akZfTbe....@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com>
Received: from mail-gh0-f199.google.com (mail-gh0-f199.google.com [209.85.160.199])
        by gmr-mx.google.com with ESMTPS id r48si12810983yhm.3.2012.06.12.06.29.46
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 12 Jun 2012 06:29:46 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3SkTXTxUJALMVakhfbnfVhWXkXobXp-akZfTbe....@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com designates 209.85.160.199 as permitted sender) client-ip=209.85.160.199;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3SkTXTxUJALMVakhfbnfVhWXkXobXp-akZfTbe....@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com designates 209.85.160.199 as permitted sender) smtp.mail=3SkTXTxUJALMVakhfbnfVhWXkXobXp-akZfTbe....@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com; dkim=pass header...@chromium.org
Received: by ghrr1 with SMTP id r1so7263562ghr.10
        for <v8-dev@googlegroups.com>; Tue, 12 Jun 2012 06:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=chromium.org; s=google;
        h=mime-version:reply-to:x-google-appengine-app-id:message-id:date
         :subject:from:to:cc:content-type;
        bh=J5PoPUvT0x3sdn2D0eP4jJdZ2YZ2EHEISTPhCNQjiYk=;
        b=IHcnFBZ+sBLAMmMA/CbfuDRE018uxC+h3agz1JhbGFPetxoRJ3AYzFxqsI/lnvdPsb
         HzueSJZIlkm5uwBArx78/eOjovVUWO0i0B1K7ObT8zS1kp3txf7+DEENA2xV+QQ9awBC
         tknWRJFyCLXrvPx2QoIujdvXeUXw92vM4hSxk=
MIME-Version: 1.0
Received: by 10.52.69.241 with SMTP id h17mr21386027vdu.5.1339507786197; Tue,
 12 Jun 2012 06:29:46 -0700 (PDT)
Reply-To: m.m.capew...@googlemail.com, da...@chromium.org, 
	svenpa...@chromium.org, v8-dev@googlegroups.com
Message-ID: <20cf307cfd3cc52ba104c2467...@google.com>
Date: Tue, 12 Jun 2012 13:29:46 +0000
Subject: Re: ARM: Add literal pool blocking to position critical code. (issue 10451037)
From: da...@chromium.org
To: m.m.capew...@googlemail.com, svenpa...@chromium.org
Cc: v8-dev@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Sven, can you please take a look? Thanks, Danno

http://codereview.chromium.org/10451037/