From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Merging MPS a.k.a. scratch/igc, yet again Date: Thu, 19 Dec 2024 19:15:17 +0000 Message-ID: <875xnf8oz1.fsf@protonmail.com> References: <87plm0msrq.fsf@telefonica.net> <87zfl4npcd.fsf@debian-hx90.lan> <87ldwnn0ny.fsf@telefonica.net> <87frmjirum.fsf@no.lan> <87h66z8tqr.fsf@protonmail.com> Reply-To: Pip Cet Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9097"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "Pip Cet via \"Emacs development discussions.\"" , Helmut Eller To: =?utf-8?Q?Gerd_M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 19 20:24:56 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tOM8l-0002Eh-Kq for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Dec 2024 20:24:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tOM7y-0007Wb-SV; Thu, 19 Dec 2024 14:24:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tOLzc-0005g2-M3 for emacs-devel@gnu.org; Thu, 19 Dec 2024 14:15:28 -0500 Original-Received: from mail-40133.protonmail.ch ([185.70.40.133]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tOLzZ-0000R7-RR for emacs-devel@gnu.org; Thu, 19 Dec 2024 14:15:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1734635720; x=1734894920; bh=MjjiXCjGWTvmZd6oUETD/U+6MZKwVn/ZwPuKPJrwTfM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=OBaIohvMDLJC91CIlOPknIn1usDP6qM13f8SZK5PqVS7ksMZuZ/ItlR7ai9dDG+8F NWOYDFi+jpPScw7H1BL2LuaiBgzZcz6OINMJdnVIkw30ALxNhgECRf+QemlMxEpV8O pkfUN85KJjpaguTzkskLSgTj1H0HCO56e4oMi2rcBB7vqHydFxYOoIzuCpSqlFeynT oSrmo6hm481SwjUB/5xZeYAdvYe35E9q61ivw76Z+g3Yu9jn/8jIHHJCua2eSKR1UM Vs979Y8Som+IDuMw5a2zVC/3K7ekm8vFzzTwqEq6GEJw5t6s8GBYol3D+bsjMTnpvq rm5AgnPtIhJdQ== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 6a0f6ae6d7dc4f002af10429a09eabbabd079d07 Received-SPF: pass client-ip=185.70.40.133; envelope-from=pipcet@protonmail.com; helo=mail-40133.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Thu, 19 Dec 2024 14:24:04 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:326763 Archived-At: Gerd M=C3=B6llmann writes: > Pip Cet via "Emacs development discussions." > writes: > >> Does anyone remember what our conclusion was wrt >> -fno-omit-frame-pointer? I seem to remember there was a patch to MPS to >> avoid relying on setjmp() to save all registers, but I'd still be >> happier if we enabled that for all MPS builds, since we don't know >> whether our MPS has the patch. > > I'm using -fno-omit-frame-pointer, but I don't remember why. I think > Helmut said something or so (in CC). We tried not using it, it caused a bug, I spent too many hours tracking that one down, so now I think we should make configure.ac always enable it, even though it should be a no-op on some architectures (I think macOS on aarch64 is one of them). I'm not sure what the right thing to do here is, though: do we want force CFLAGS to include -fno-omit-frame-pointer, or set it only when CFLAGS isn't specified explicitly, or is looking at user-provided CFLAGS and complaining about them the right thing to do? Pip