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.bugs Subject: bug#46881: 28.0.50; pdumper dumping causes way too many syscalls Date: Fri, 05 Mar 2021 09:19:00 +0200 Message-ID: <83a6riysnv.fsf@gnu.org> References: <83r1kw6b06.fsf@gnu.org> <90e99fc5-280d-63bb-9bc4-3efe89b9f9e2@dancol.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18020"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46881@debbugs.gnu.org, eggert@cs.ucla.edu To: Pip Cet Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 05 08:20:10 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1lI4ks-0004a8-5H for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 05 Mar 2021 08:20:10 +0100 Original-Received: from localhost ([::1]:58120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lI4kr-000149-6q for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 05 Mar 2021 02:20:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35548) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lI4kk-00013w-5W for bug-gnu-emacs@gnu.org; Fri, 05 Mar 2021 02:20:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49325) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lI4kj-0004Jg-T2 for bug-gnu-emacs@gnu.org; Fri, 05 Mar 2021 02:20:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lI4kj-00069p-Na for bug-gnu-emacs@gnu.org; Fri, 05 Mar 2021 02:20:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 05 Mar 2021 07:20:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46881 X-GNU-PR-Package: emacs Original-Received: via spool by 46881-submit@debbugs.gnu.org id=B46881.161492876623613 (code B ref 46881); Fri, 05 Mar 2021 07:20:01 +0000 Original-Received: (at 46881) by debbugs.gnu.org; 5 Mar 2021 07:19:26 +0000 Original-Received: from localhost ([127.0.0.1]:60870 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lI4kA-00068n-2A for submit@debbugs.gnu.org; Fri, 05 Mar 2021 02:19:26 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45688) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lI4k7-00068X-SO for 46881@debbugs.gnu.org; Fri, 05 Mar 2021 02:19:25 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52967) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lI4k2-0003sk-6I; Fri, 05 Mar 2021 02:19:18 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3748 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lI4k0-0007wX-1s; Fri, 05 Mar 2021 02:19:18 -0500 In-Reply-To: (message from Pip Cet on Fri, 5 Mar 2021 02:30:13 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:201498 Archived-At: > From: Pip Cet > Date: Fri, 5 Mar 2021 02:30:13 +0000 > Cc: Eli Zaretskii , Paul Eggert , 46881@debbugs.gnu.org > > > It looks fine, but wouldn't dumping to a FILE* (with internal buffering) > > do the same basic thing in a simpler way? > > I initially set out to do that, but decided against it. We don't just > write sequentially (when FILE I/O helps, a little), we also have the > seek-and-fixup phase, and it didn't seem any simpler at that point.. I'm not sure I understand: what's wrong with fseek?