mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Clang static analyser results
Date: Thu, 3 Mar 2016 14:30:23 -0800	[thread overview]
Message-ID: <026CC71A-1873-4CD0-8738-2A542BE5FFB2@gmail.com> (raw)
In-Reply-To: <20160303192100.GX9349@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]


> On Mar 3, 2016, at 11:21 AM, Rich Felker <dalias@libc.org> wrote:
> 
> On Wed, Mar 02, 2016 at 10:56:33PM -0800, Khem Raj wrote:
>> 
>>> On Mar 2, 2016, at 10:32 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> 
>>> All,
>>> 
>>> I ran clang static analyser on tip of git today for x86_64 build. The results are here
> 
> Thanks!
> 
>>> https://busybox.net/~kraj/scan-build-2016-03-02-222206-32091-1/
>> 
>> and
>> 
>> https://busybox.net/~kraj/scan-build-2016-03-02-225259-30448-1/
>> 
>> is arm cross built with clang as CC
> 
> Any idea why the results are different for arm? Most of the code where
> things are reported does not differ by arch.

ARM is cross compiled using clang itself while x86_64 was using native gcc.
another difference is that arm was using clang 3.8 for static analysis while
x86_64 was using clang 3.7
> 
> I think everything reported has been investigated before and found to
> be false positives. Do any of them look new/interesting?

I did not look into details myself yet, its good to know that nothing new is found
we want to keep it that way

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

      reply	other threads:[~2016-03-03 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  6:32 Khem Raj
2016-03-03  6:56 ` Khem Raj
2016-03-03 19:21   ` Rich Felker
2016-03-03 22:30     ` Khem Raj [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=026CC71A-1873-4CD0-8738-2A542BE5FFB2@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).