From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: sparse-llvm potential error in linearized output Date: Sun, 12 Mar 2017 16:52:12 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-io0-f172.google.com ([209.85.223.172]:35712 "EHLO mail-io0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933837AbdCLQwO (ORCPT ); Sun, 12 Mar 2017 12:52:14 -0400 Received: by mail-io0-f172.google.com with SMTP id z13so72717866iof.2 for ; Sun, 12 Mar 2017 09:52:13 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Linus Torvalds Cc: Sparse Mailing-list On 12 March 2017 at 16:27, Linus Torvalds wrote: > On Mar 12, 2017 6:04 AM, "Dibyendu Majumdar" wrote: > load.64 %r3 <- 0[randomletters] > > > Looks fine to me. > > You have a variable called randomletters, and it's a pointer to a char. That > 64-bit load just loads that pointer value from the variable into %r3. > > The sparse linearized format only has one memory access model: load with > constant offset. The base can either be a symbol address (like in this case) > or a register. > Ok thanks. Regards Dibyendu