From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) by sourceware.org (Postfix) with ESMTPS id 6BC6E3858430 for ; Mon, 10 Oct 2022 18:39:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6BC6E3858430 Received: by mail-pl1-x632.google.com with SMTP id c20so1545340plc.5 for ; Mon, 10 Oct 2022 11:39:26 -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=du9fqmK8zOisX50yIX9qk0+y2vZS1FrXd+3KhNc8J50=; b=iMeaSNapwZzAGKxBjJGlbi3Iyqk2ncIBZEG7IY8LzdJ48wlwF8CnkzD2NFrOnrxtnv HhFAtlyxUicX3zYF1ELDRGmFugn+oZeUll6lKC9sNg6xxjPAIMpouFF9OSfVQuq/oAwV uzavTJfIj4NBxh2MsBDkHut94czfv+Un73isFD8KuO7N4MOVCbjsf/+tvc+jY+sj77wj zZ2sLjfvykBQkyxcO3Jh3uR/e6LHg1546jjKsOU7xZOnhutboYAb/aYz6wqDNKq7Z1II VfvYIySDQCmnkeLXFLLn8XKKSMtbveMKi9wMmJMWFqrzg/yYRBfPLWb4c1OiBtgbi6z+ KObQ== X-Gm-Message-State: ACrzQf3bYO/N0Fc6FBUuV1q4uBG7oMayFhE9OvgoGHXVnKO+P41jsm9O v+sn67yqKpCbzoCRJrO1dJutG6837Hpf X-Google-Smtp-Source: AMsMyM4uUl9bzNoVISxh6XywdFvt5EAMigllFw7qM384RIY4wasEI8dsWO4d0OjG0X2JbQXFe0+oaw== X-Received: by 2002:a17:90a:5308:b0:20b:1eae:c94e with SMTP id x8-20020a17090a530800b0020b1eaec94emr23357963pjh.88.1665427165388; Mon, 10 Oct 2022 11:39:25 -0700 (PDT) Received: from takamaka.gnat.com ([184.69.131.86]) by smtp.gmail.com with ESMTPSA id n6-20020a17090a670600b00203917403ccsm6336475pjj.1.2022.10.10.11.39.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Oct 2022 11:39:24 -0700 (PDT) Received: by takamaka.gnat.com (Postfix, from userid 1000) id 0CF1A81490; Mon, 10 Oct 2022 11:39:24 -0700 (PDT) Date: Mon, 10 Oct 2022 11:39: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: X-Spam-Status: No, score=-4.3 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 18:39:28 -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. Good news; I just received confirmation that the process is complete :-). > 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. -- Joel