From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A6C4D384233B; Tue, 13 Dec 2022 23:16:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A6C4D384233B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670973361; bh=6V1afflN8p+L6o0Mvj7Oxd6UVJhVXB0F98ylmgkn5sE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KuTqfOtoCVuxI4bHWdW+XvuvMB3NCE5/T4ArWlL4L/dXs6awf0QvDuiLrUIMaoVuN Vd0eBCRMMIqZw1s2inmRaS1vBOz3KuovjFJh5ScGKbhzBTiiB/WDDfsFzsB1V52UbW XlfN9kGONiH/wtrddtMNpw9gD9x0/k7AVGGJ33w0= From: "nars at yottadb dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/29863] Segmentation fault in memcmp-sse2.S if memory contents can concurrently change Date: Tue, 13 Dec 2022 23:16:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nars at yottadb dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29863 --- Comment #14 from Narayanan Iyer --- (In reply to Noah Goldstein from comment #13) >=20 > Can you test the following dif: > ``` > @@ -308,7 +308,7 @@ L(ret_nonzero_vec_end_0): > setg %dl > leal -1(%rdx, %rdx), %eax > # else > - addl %edx, %eax > + addq %rdx, %rax > movzbl (VEC_SIZE * -1 + SIZE_OFFSET)(%rsi, %rax), %ecx > movzbl (VEC_SIZE * -1 + SIZE_OFFSET)(%rdi, %rax), %eax > subl %ecx, %eax >=20 > ``` >=20 > If that fixes things I'm okay making the change. >=20 > I'm opposed to explicitly supporting it, but am happy > to try and make this failure from the unsupported > usage less dramatic. This change sounds much better. Is there a url that describes how to build glibc from source and use it in = my application? --=20 You are receiving this mail because: You are on the CC list for the bug.=