From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Merging MPS a.k.a. scratch/igc, yet again Date: Fri, 20 Dec 2024 08:39:41 +0200 Message-ID: <86v7vekgcy.fsf@gnu.org> References: <87plm0msrq.fsf@telefonica.net> <87zfl4npcd.fsf@debian-hx90.lan> <87ldwnn0ny.fsf@telefonica.net> <87frmjirum.fsf@no.lan> <87h66z8tqr.fsf@protonmail.com> <875xnf8oz1.fsf@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33360"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pipcet@protonmail.com, emacs-devel@gnu.org, eller.helmut@gmail.com To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 20 07:40:36 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 1tOWgd-0008Yg-H1 for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Dec 2024 07:40:35 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tOWft-0007uH-PC; Fri, 20 Dec 2024 01:39:49 -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 1tOWfp-0007tg-E6 for emacs-devel@gnu.org; Fri, 20 Dec 2024 01:39:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tOWfp-0004JA-5a; Fri, 20 Dec 2024 01:39:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=Pp//fBUzZDjYyXN42g2Kb/T89zZyfow96nPhbDVQ/EA=; b=Bb9X/5iGpaEylL2+Cpkk OUnf052bLpGDdYOCG9+p0Hw5pagBuH2VV4Kz7f/2qdnV07TQ+PztWrQ46KOa33LFuiM8Dy8bfxn5f Nr7KTw/cey8e+Aqc4fzcNTaNDW+maBj0xMv9VGVnKdgC63MN2LKgffS/gCAQKrHk+cWejwabdy5ac M2gAeJyJFeVzWdscrKgu0hx0VrfWZjDgo0L7zkin57aM32Z7qRsBalCw7xfQ8H3ehNvkJeCPKmbLc Qgkr49Q7xaQIMZtroei3ezGbw5NhbJKnmQOfyNRlIknX3+d0sIi4Mcr53z5+iQZCjvwS2wKr+ip9U 162D5QN+m7QiAA==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Thu, 19 Dec 2024 20:57:45 +0100) 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:326780 Archived-At: > From: Gerd Möllmann > Cc: "Pip Cet via \"Emacs development discussions.\"" , > Helmut Eller > Date: Thu, 19 Dec 2024 20:57:45 +0100 > > Pip Cet writes: > > > Gerd Möllmann 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 agree. > > And maybe we should tell testers of the branch to stick to the compiler > options Emacs uses by default for now? To reduce the number of moving > parts, at least for a while. Don't what guarantees Emacs currently gives > of working with what compiler options. I think sticking to the default options is indeed a good idea. > > 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? > > I'd force it, but I'm reckless :-). Agreed.