Date: Sun, 5 Mar 2017 03:02:24 -0800 From: Mark Millard <markmi@dsl-only.net> To: Andrew Gierth <andrew@tao11.riddles.org.uk> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Is CPUTYPE=cortex-A7 supposed to work? Message-ID: <70AE704A-C9FF-4742-88E9-147CD5B77BE8@dsl-only.net> In-Reply-To: <87h93814rb.fsf@news-spur.riddles.org.uk> References: <871suc3nv8.fsf@news-spur.riddles.org.uk> <CANCZdfq4EwH%2B_9FVNai8s6Y-gdTjHJ8dNkJwSrnF%2BSAkdwvYdg@mail.gmail.com> <87tw7820fc.fsf@news-spur.riddles.org.uk> <644D1F49-BF5D-409D-BFC4-4F7E6E73085B@dsl-only.net> <87lgsk1udz.fsf@news-spur.riddles.org.uk> <9677298B-5A5E-44BF-928E-28DDDADB310A@dsl-only.net> <87h93814rb.fsf@news-spur.riddles.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Mar-5, at 2:01 AM, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote: >>>>>> "Mark" == Mark Millard <markmi at dsl-only.net> writes: > >>> 3. The errors aren't consistent at all. For example, sometimes I run >>> openssl speed rsa512 and it succeeds without error. When testing >>> with git, the failures were not always at the same place. > > Mark> Interesting. My context had MALLOC_PRODUCTION. I wonder if > Mark> without that and having junk filled in systematically might > Mark> produce more stable results. (I've no specific evidence that this > Mark> would make a difference.) > > I don't think this can explain my results with git; openssl's sha1 > doesn't call malloc (or any library function other than memcpy, memset, > OPENSSL_cleanse), and I have logs of the data being hashed that show the > wrong results returned. Also, I've checked that while these hashes are > being done, there are no other threads in the process. > > -- > Andrew. FYI: I've updated to -r314687 (so now clang 4.0 based) and openssl speed still gets the same failures. (By contrast a pine64+ 2 GiByte [an arm64] worked fine.) I have not tried a normal build without the -mcpu=cortex-a7 use (or equivalent). Have you? === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70AE704A-C9FF-4742-88E9-147CD5B77BE8>