From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by sourceware.org (Postfix) with ESMTPS id 5B0C6385AC3F for ; Mon, 10 Oct 2022 14:45:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5B0C6385AC3F Received: by mail-pj1-x102f.google.com with SMTP id a5-20020a17090aa50500b002008eeb040eso11787472pjq.1 for ; Mon, 10 Oct 2022 07:45:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3MpI1hp0wDFY+4QuZb2vrjy7xKX07oaBPjhDRqZUMdI=; b=C/L3BQ5wDdbSg/ZK6H8j42uBPSZo1YVAiZShdTCCg4mlxT3eF5oWTu8pbGR206g2Qp Y39cZpE6M0PBfLCzegkx0RLH1DpbMtPf+6uGMnqNA9Rx2JgsAkqje48qd85yBYmWAB0P QX9TeVpxMkU7Osc6XWyxwybuZd5BeOnr9dqec3I62UM0B/AR7bs+/MiluprPOVzXMAhs I8GevccUYdzpVH/H34IQkmqu2LKhC7kOUjABzCDl2xtw2j88dkPLHtu9Whtth9bFrYBU 8HYQM/IG/eEYZr44OOizIpyyaSynr3YVmQ40quKgUeo/UH0lF5Z9eJ3Gos402eYGq70j k9XQ== X-Gm-Message-State: ACrzQf0kofLR1O+2edXqn2q+m5ovJe2kGaTPSpnK3OtwvYT32w+cUGWi xszYi5QM2rVYyS9A7AXRWMIuYd0JPYRX X-Google-Smtp-Source: AMsMyM4DFqlCPx8m1LYMTRjD7jkpokeLsQYTypbz5N6AP0DPbiCfmSqVvUNzSdJlKnDWzOxz4DozvA== X-Received: by 2002:a17:903:11c3:b0:17a:e62:16e8 with SMTP id q3-20020a17090311c300b0017a0e6216e8mr20218103plh.137.1665413126301; Mon, 10 Oct 2022 07:45:26 -0700 (PDT) Received: from takamaka.gnat.com ([184.69.131.86]) by smtp.gmail.com with ESMTPSA id s20-20020aa78bd4000000b00562f6df42f1sm4800179pfd.152.2022.10.10.07.45.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Oct 2022 07:45:25 -0700 (PDT) Received: by takamaka.gnat.com (Postfix, from userid 1000) id EBC1281490; Mon, 10 Oct 2022 07:45:24 -0700 (PDT) Date: Mon, 10 Oct 2022 07:45:24 -0700 From: Joel Brobecker To: Torbjorn SVENSSON Cc: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: GDB 13 release -- 2022-10-01 update Message-ID: References: <225620a3-5eb4-eeef-e0b7-86f18817216e@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <225620a3-5eb4-eeef-e0b7-86f18817216e@foss.st.com> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, 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.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2022 14:45:34 -0000 > > > I would like to land 2 patches for Cortex-M before the release. > > > > > > * https://sourceware.org/bugzilla/show_bug.cgi?id=28549 > > > > Can you provide more information about this one? > > > > - What's the motivation behind suggesting this PR? This will be > > important for us to know should resolution of this PR be delayed. > > The motivation is simply that with the last improvements on the stack unwind > on Cortex-M, the stack unwind can take a considerable amount of time > (endless?) if the CPU is in lockup state. > > > - Have the latest version of the patches been submitted for review? > > If yes, can you provide URLs? In reading the PR, I am not really > > sure how many patches we are talking about, and where those patches > > migth be residing. > > I think Luis has the most up to date status here. Thomaz has created a > single patch (https://sourceware.org/bugzilla/attachment.cgi?id=13853) that > would handle the problematic case, but as there is no copyright on file for > Tomaz, he needed to send one to FSF. A few weeks back, Thomaz did just that, > but there has been no response from FSF. > The patch is in a sort-of-working state. There are some minor things to be > addressed, but before the patch can be shared on the ML, the copyright pat > must be handled. OK; let's see what happens with the FSF assignment process. It seems indeed desirable for us to include it in GDB 13, but I don't think it will be blocking us if the patch gets delayed because we're waiting for the assignment to come through (looking at progress on the other issues, I think the FSF still has time). Worst case scenario, if everything but this patch is done, we can start by branching and creating our first pre-release. I think it'll be relatively easy and safe to backport once the patch is approved. Just for the avoidance of doubt, I assume you guys are finalizing the patch in parallel to waiting for the FSF to get back to us, right? Ideally, as soon as we have the paperwork done, the patch gets pushed. Thank you, -- Joel