From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id JX90Efz9wmJkBgwAWB0awg (envelope-from ) for ; Mon, 04 Jul 2022 10:49:32 -0400 Received: by simark.ca (Postfix, from userid 112) id 364021E22B; Mon, 4 Jul 2022 10:49:32 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=ibruWhPE; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (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 simark.ca (Postfix) with ESMTPS id 62A2B1E222 for ; Mon, 4 Jul 2022 10:49:31 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 03F98385BAE1 for ; Mon, 4 Jul 2022 14:49:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03F98385BAE1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1656946171; bh=kFCqRnSrHu4FUAlD3xQLfHyiK2eMFj34vTvHsmN0ySA=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=ibruWhPEULcG3BvrHqMyvGIU9Ep4HBg6IOHBhD/wSm5vkVnMOEBd5IVM6YWjL7EU4 Mw5eUzP7fscBJ1vq8xKxspnWv2lUWLMlJNo5gQHnCZFhvZ6zUBxjA2eF2+3DQ5uPNP q+0WEtQX7wrlE18xJJbR0kKogv8avE1a+YsZ91OY= 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 A7E493854155 for ; Mon, 4 Jul 2022 14:49:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A7E493854155 Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-55-q0FY38iLPsK3dPQUYXa_ew-1; Mon, 04 Jul 2022 10:49:09 -0400 X-MC-Unique: q0FY38iLPsK3dPQUYXa_ew-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 00D711C0519D; Mon, 4 Jul 2022 14:49:09 +0000 (UTC) Received: from [10.97.116.25] (ovpn-116-25.gru2.redhat.com [10.97.116.25]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3289E1121315; Mon, 4 Jul 2022 14:49:08 +0000 (UTC) Message-ID: Date: Mon, 4 Jul 2022 11:49:06 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PING 2] [PATCH 0/4] Adapt Fortran testsuite for ifort To: "Kempke, Nils-Christian" , Enze Li , "gdb-patches@sourceware.org" References: In-Reply-To: X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Bruno Larsen via Gdb-patches Reply-To: Bruno Larsen Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" This is likely a problem with the rest of your emailing chain (either client or outgoing server) I remember when using the Outlook web-based interface, if I removed the "Re:" from the subject, it would remove the In-Reply-To header, which messed up the threading. I think Exchange was at fault, but I'm not sure, someone else fixed this for me... Cheers! Bruno Larsen On 7/4/22 11:43, Kempke, Nils-Christian via Gdb-patches wrote: > To clarify (and please correct me, if my way of pinging is wrong): > > I normally hit 'reply all', either on the original message if this was the first > ping or on the latest ping if this was a subsequent ping. Then, I modify the subject > to 'RE: [PING N] ORIGINAL TITLE' and add my little ping body to the email. Then I > send that message. > > Is this wrong? > > I see that I somehow messed up the first ping for this message (in June) - it is not listed > in the same thread as the original message - so apparently it was not a reply to it.. > I might have removed the 'RE:' in the title of that messge? > > But anyhow, this is how I understood > > https://sourceware.org/gdb/wiki/ContributionChecklist#Ping_and_keep_pinging > > and Joels mail on the patches list. > > Cheers, > Nils > >> -----Original Message----- >> From: Gdb-patches > christian.kempke=intel.com@sourceware.org> On Behalf Of Kempke, Nils- >> Christian via Gdb-patches >> Sent: Monday, July 4, 2022 4:04 PM >> To: Enze Li ; gdb-patches@sourceware.org >> Subject: RE: [PING 2] [PATCH 0/4] Adapt Fortran testsuite for ifort >> >> Hi Enze, >> >> Yes, this was also not what I intended. Seems like I already messed that up in >> my first ping. >> >> Thanks for pointing it out, I'll ping the original message again. This thread can >> be ignored then. >> >> Cheers, >> Nils >> >>> -----Original Message----- >>> From: Enze Li >>> Sent: Monday, July 4, 2022 3:54 PM >>> To: Kempke, Nils-Christian ; gdb- >>> patches@sourceware.org >>> Subject: Re: [PING 2] [PATCH 0/4] Adapt Fortran testsuite for ifort >>> >>> Hi Nils, >>> >>> A friendly reminder that it is not easy to review patches outside of >>> the threaded email. It would be nice if you could reply "PING" >>> directly in the threaded email. That way, others can see the patches >>> *directly* instead of searching through the mailing list. >>> >>> Thanks, >>> Enze >>> >>> On Mon, 2022-07-04 at 10:29 +0000, Kempke, Nils-Christian via Gdb- >>> patches wrote: >>>> Ping! >>>> >>>> Thanks, >>>> Nils >>>> >>>>> -----Original Message----- >>>>> From: Gdb-patches >>>> christian.kempke=intel.com@sourceware.org> On Behalf Of Kempke, >>>>> Nils- >>>>> Christian via Gdb-patches >>>>> Sent: Monday, June 27, 2022 6:59 AM >>>>> To: gdb-patches@sourceware.org >>>>> Subject: [PING] [PATCH 0/4] Adapt Fortran testsuite for ifort >>>>> >>>>> Ping! >>>>> >>>>> Thanks, Nils >>>>> >>>>>> -----Original Message----- >>>>>> From: Kempke, Nils-Christian >>>>>> Sent: Friday, June 10, 2022 5:45 PM >>>>>> To: gdb-patches@sourceware.org >>>>>> Cc: Kempke, Nils-Christian >>>>>> Subject: [PATCH 0/4] Adapt Fortran testsuite for ifort >>>>>> >>>>>> Hi, >>>>>> >>>>>> there were a few places in the testsuite where ifort's behavior >>>>>> was >>>>>> FAILing the tests and where I think this is not the result of an >>>>>> ifort >>>>>> bug but rather of a testsuite not forgiving enough. >>>>>> >>>>>> The attached patches should not change the behavior for any other >>>>>> compiler, and I could not find any regressions with gfortran/ifx >>>>>> (tested >>>>>> with unix, unix/m32, native-gdbserver and native-extended- >>>>>> gdbserver). >>>>>> >>>>>> For ifort this series improves testsuite performance if compared >>>>>> to the >>>>>> current master: >>>>>> >>>>>> master before series: >>>>>> >>>>>>                 === gdb Summary === >>>>>> >>>>>>   # of expected passes            5771 >>>>>>   # of unexpected failures        238 >>>>>>   # of unknown successes          1 >>>>>>   # of known failures             1 >>>>>>   # of untested testcases         1 >>>>>>   # of unresolved testcases       3 >>>>>>   # of unsupported tests          5 >>>>>>   # of duplicate test names       3 >>>>>> >>>>>> master after series: >>>>>> >>>>>>                 === gdb Summary === >>>>>> >>>>>>   # of expected passes            5847 >>>>>>   # of unexpected failures        161 >>>>>>   # of known failures             1 >>>>>>   # of untested testcases         1 >>>>>>   # of unresolved testcases       3 >>>>>>   # of unsupported tests          5 >>>>>>   # of duplicate test names       3 >>>>>> >>>>>> >>>>>> Any feedback is appreciated, >>>>>> >>>>>> Cheers, >>>>>> Nils >>>>>> >>>>>> Nils-Christian Kempke (4): >>>>>>   testsuite, fortran: make mixed-lang-stack less compiler >>>>>> dependent >>>>>>   testsuite, fortran: Remove self assignment non-statements >>>>>>   testsuite, fortran: adapt tests for ifort's 'start' behavior >>>>>>   testsuite, fortran: make kfail gfortran specific >>>>>> >>>>>>  gdb/testsuite/gdb.fortran/array-slices-bad.exp    |  5 ++++- >>>>>>  gdb/testsuite/gdb.fortran/function-calls.exp      |  4 +++- >>>>>>  gdb/testsuite/gdb.fortran/library-module-lib.f90  |  2 +- >>>>>>  gdb/testsuite/gdb.fortran/library-module-main.f90 |  2 +- >>>>>>  gdb/testsuite/gdb.fortran/mixed-lang-stack.exp    |  9 ++++++++- >>>>>>  gdb/testsuite/gdb.fortran/module.f90              | 11 ++++++--- >>>>>> -- >>>>>>  gdb/testsuite/gdb.fortran/vla-type.exp            |  5 +++-- >>>>>>  7 files changed, 26 insertions(+), 12 deletions(-) >>>>>> >>>>>> -- >>>>>> 2.25.1 >>>>> >>>>> Intel Deutschland GmbH >>>>> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany >>>>> Tel: +49 89 99 8853-0, www.intel.de  >>>>> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon >>>>> Silva >>>>> Chairperson of the Supervisory Board: Nicole Lau >>>>> Registered Office: Munich >>>>> Commercial Register: Amtsgericht Muenchen HRB 186928 >>>> >>>> Intel Deutschland GmbH >>>> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany >>>> Tel: +49 89 99 8853-0, www.intel.de  >>>> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon >>>> Silva >>>> Chairperson of the Supervisory Board: Nicole Lau >>>> Registered Office: Munich >>>> Commercial Register: Amtsgericht Muenchen HRB 186928 >>>> >> >> Intel Deutschland GmbH >> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany >> Tel: +49 89 99 8853-0, www.intel.de >> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva >> Chairperson of the Supervisory Board: Nicole Lau >> Registered Office: Munich >> Commercial Register: Amtsgericht Muenchen HRB 186928 > Intel Deutschland GmbH > Registered Address: Am Campeon 10, 85579 Neubiberg, Germany > Tel: +49 89 99 8853-0, www.intel.de > Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva > Chairperson of the Supervisory Board: Nicole Lau > Registered Office: Munich > Commercial Register: Amtsgericht Muenchen HRB 186928