From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id EFB403849AEF for ; Sat, 13 Apr 2024 15:03:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EFB403849AEF Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org EFB403849AEF Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713020621; cv=none; b=VG7ol82XvjRmq9gcyuzzin0/Li5ZcM+hRt3iN53c14xS+zkW1g859zBAOeWD7qiyYpmKg3rYBQ7wArxI3J93JFKyDlIw1WPMMWnisM32ILkMmBmkp54P1skWrdi3Vll/SFcfKTy8KBPVHKmyu59XjX/0Oh3khQQUs5CjCP4/Hi4= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713020621; c=relaxed/simple; bh=aMbFvZ9YREPX76IYSMawbFJOmFCWL9M664BT756ZBDg=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=Nw56KBW/aKELhwYCYzaZiUHwLB0+1DK7dY7ORWJBX9IiD4LYabUUOFtGFrrWIomsLWseg8BZekX9/IyV8AG0ElSM1b3qlmDb2T1XOm0UuDVchf910CqojFBSgRkkwPqObZrVMYxBKCiBsGmvo4soo/SF0oN+h838gAkFJBL/POU= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1713020619; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gByr9Bz1NZMgL/Bwf7LK5fkS8oeoAxu0870GslCxtTk=; b=I7y/dnl2XK3JUqQMEhR071V4w5UuDYHcooArTCmJy1V0pIdaqD2dcvEk3wh3lxAMm03+sg k45W3NX1r7NDDFAmiCZXg5SmUURsFVUae2e/VgRo4bJhl1fZx9ZoJ6QgDBya/pkMC94Lfk YcsW84pXd2lh2BOqjzaMEaaFwkXdHG0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-353-2evqp98QNq2DbxLV_uPeyg-1; Sat, 13 Apr 2024 11:03:36 -0400 X-MC-Unique: 2evqp98QNq2DbxLV_uPeyg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CD988802E4D; Sat, 13 Apr 2024 15:03:35 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.193.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F211BC01593; Sat, 13 Apr 2024 15:03:34 +0000 (UTC) From: Florian Weimer To: "H.J. Lu" Cc: libc-alpha@sourceware.org, Sunil K Pandey Subject: Re: [PATCH] Revert "x86_64: Suppress false positive valgrind error" In-Reply-To: (H. J. Lu's message of "Sat, 13 Apr 2024 07:58:39 -0700") References: <87a5lx2u9a.fsf@oldenburg.str.redhat.com> Date: Sat, 13 Apr 2024 17:03:29 +0200 Message-ID: <875xwl2tku.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * H. J. Lu: > On Sat, Apr 13, 2024 at 7:49=E2=80=AFAM Florian Weimer wrote: >> >> This reverts commit a1735e0aa858f0c8b15e5ee9975bff4279423680. >> >> The test failure is a real valgrind bug that needs to be fixed before >> valgrind is usable with a glibc that has been built with >> CC=3D"gcc -march=3Dx86-64-v3". The valgrind fix addresses the observed >> test failure as well. >> >> Upstream bug: >> >> Tested on x86_64-linux-gnu with and without CC=3D"gcc -march=3Dx86-64-v3= ". >> The elf/tst-valgrind-smoke tests again fails with an unpatched valgrind, >> and the proposed upstream patch fixes it. (Apparently, valgrind >> matches on soname, and not the file name, which is ld.so in the test.) > > Please clarify that your patch fixes the glibc valgrind test by not using > strcmp-avx2.S in the valgrind test. Sorry, clarify where? In the commit message here? On the upstream bug? My valgrind patch replaces the strcmp implementation in ld.so with its own. Thanks, Florian