Message ID | 20241129162802.1216434-1-stephan.rohr@intel.com |
---|---|
Headers |
Return-Path: <gdb-patches-bounces~patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 131363858403 for <patchwork@sourceware.org>; Fri, 29 Nov 2024 16:28:29 +0000 (GMT) X-Original-To: gdb-patches@sourceware.org Delivered-To: gdb-patches@sourceware.org Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.17]) by sourceware.org (Postfix) with ESMTPS id B5EC73858C50 for <gdb-patches@sourceware.org>; Fri, 29 Nov 2024 16:28:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B5EC73858C50 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=intel.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org B5EC73858C50 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=198.175.65.17 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1732897689; cv=none; b=x/kr8wL0EleHVqXKKpdQoAYpCofq7u4zhNxo/X8jroWJxavy18o8iTQwLSFrEtGHWltmKgTF8ehQVTRXP/hmt4bfLcPb6urwQQSDincTU+GJ6nf5VBCheSMJtyPN0e7VXYABTRlMcvZG+O8e+sVyeFN7aUX7kdTwimqhSCY79hI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1732897689; c=relaxed/simple; bh=hxPD/fF4+77b8vJHNYDpIzY/Gu0wt/1QYCONeUTAtxA=; h=DKIM-Signature:From:To:Subject:Date:Message-Id:MIME-Version; b=umsdjw/kxHs4Zok6cSRyRKh6iCkSjfW3etc2skArNbBIGpnkGadY3j2/POi0uh9jfDVEBJ2llEvCd1JQC3jyc9uhZlg0NHaYyvP8j1zWpuPJJvMt1Udhv1QYaimbSnd9KC77nweqiG4ii+SoxKwjAZFIs5LbkRfxaByafnxIW6g= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5EC73858C50 Authentication-Results: sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=erodkG7B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1732897689; x=1764433689; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=hxPD/fF4+77b8vJHNYDpIzY/Gu0wt/1QYCONeUTAtxA=; b=erodkG7B3toMiNfEnrBH8afftWSdkyDh1q1xrP0U9Mns+5dvXwniJfjv 2LHxJHEFoEYzUawhHZhNSuPxQUYffrjJjh9Ar2pOAlvgBF9dKUnrXULki pFPtZTWtrbDv18fDYQSFZg6ymb4yEWrWZRRjLOpKzGy3a0Bh5L0VTABxx wQbL3EgI6Wm9nQZPTFS3xdLDJttxu/OFK/D2TTU/aGQJsWK/OYlizIGII fF1pVAnZ694ZjBFByvSdj3cPvEV8gGFnP/nBIYo7CNmfJK1y0JXHE5CyJ /f1UVCaZ2lY39LP60P3bB+uk2xsCXXwpfW2RO+KhCdTb2FtapSAcKMLzI Q==; X-CSE-ConnectionGUID: apBz9wHAQKKK7kD0jyhp7g== X-CSE-MsgGUID: R1bf3+02Se6blCf+Y5yHKw== X-IronPort-AV: E=McAfee;i="6700,10204,11271"; a="33189345" X-IronPort-AV: E=Sophos;i="6.12,196,1728975600"; d="scan'208";a="33189345" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by orvoesa109.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2024 08:28:07 -0800 X-CSE-ConnectionGUID: 4Fl5MpM1QcSHidX4lP2bCg== X-CSE-MsgGUID: KoxptHB3SeuKE6ZZ5isPLA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,196,1728975600"; d="scan'208";a="115799430" Received: from 984fee0031af.jf.intel.com (HELO localhost) ([10.165.54.65]) by fmviesa002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2024 08:28:07 -0800 From: Stephan Rohr <stephan.rohr@intel.com> To: gdb-patches@sourceware.org Subject: [PATCH 0/1] gdb, testsuite: add missing return statements Date: Fri, 29 Nov 2024 08:28:01 -0800 Message-Id: <20241129162802.1216434-1-stephan.rohr@intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, 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 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=subscribe> Errors-To: gdb-patches-bounces~patchwork=sourceware.org@sourceware.org |
Series |
gdb, testsuite: add missing return statements
|
|
Message
Rohr, Stephan
Nov. 29, 2024, 4:28 p.m. UTC
Hi all, this patch adds missing return statements in * gdb.threads/process-exit-status-is-leader-exit-status.c * gdb.threads/next-fork-exec-other-thread.c These are just cosmetics changes to omit compiler warnings, e.g.: $ gcc -Wall process-exit-status-is-leader-exit-status.c process-exit-status-is-leader-exit-status.c: In function ‘start’: process-exit-status-is-leader-exit-status.c:46:1: warning: no return statement in function returning non-void [-Wreturn-type] 46 | } | ^ I appreciate your feedback. Thanks Stephan Rohr, Stephan (1): testsuite, threads: add missing return statements gdb/testsuite/gdb.threads/next-fork-exec-other-thread.c | 4 ++++ .../gdb.threads/process-exit-status-is-leader-exit-status.c | 1 + 2 files changed, 5 insertions(+)
Comments
On 2024-11-29 11:28, Stephan Rohr wrote: > Hi all, > > this patch adds missing return statements in > > * gdb.threads/process-exit-status-is-leader-exit-status.c > * gdb.threads/next-fork-exec-other-thread.c > > These are just cosmetics changes to omit compiler warnings, e.g.: > > $ gcc -Wall process-exit-status-is-leader-exit-status.c > process-exit-status-is-leader-exit-status.c: In function ‘start’: > process-exit-status-is-leader-exit-status.c:46:1: warning: no return statement > in function returning non-void [-Wreturn-type] > 46 | } > | ^ > > I appreciate your feedback. Thanks, this is OK: Approved-By: Simon Marchi <simon.marchi@efficios.com> However, I suggest to put the information up there (notably the compiler warning) in the commit message. For a single patch like this, you don't really need a cover letter, all the info can be in the commit message, where it will be kept for eternity in the git repo. Simon