From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) by sourceware.org (Postfix) with ESMTPS id 6A60D3858D39; Sun, 26 Dec 2021 13:14:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6A60D3858D39 Received: by mail-wr1-x42c.google.com with SMTP id w20so17986854wra.9; Sun, 26 Dec 2021 05:14:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=akj3MthGqoP3xFU3wjB0pa+UWf4Cmr50483VYCw63nM=; b=j66nFxR+QzY6aDuaK9jNegMchv0XVoll5JVTAWxdopb6l7hHP8DtoeLqWGHOs33Hoz 1NJOqJOfEnjH9U5Hy5O8s0GaNC+m4JCYp7GKVweZsEugnGJSpoY+FKl9a4pGlRSNJUw8 Hq5EdRmkMdc6CwRwf56OYr8BIMkb+HW0ggrEBcx/cL2d7C9gkxnsLFPZxhIVK0KjHPkJ 9QLejxpxKv0lB06X7IF/GG6xtYhL4UoctRRuWRU0YO6yLSaBI7gclPkvOICPYCiOMLAZ EJ4O8UCkc90hGLalXM4oRzCR38+UNAmjgE1mR096HCZheFIu9abs1yonxmrBVr5PFJQM Evqw== X-Gm-Message-State: AOAM5328stoTS5E6cse6VCp6MxqQNF0251Fhdjzks6YZG58F+7boWM8K 67sM/8GMqx8fuTx1HbIzoqk= X-Google-Smtp-Source: ABdhPJzDJSdu01gI91VE2Rafjt+OMHG1G+W+GXP6J4CFe/glEmtkf/nKJT/81aLBLBu9PABQlMscGg== X-Received: by 2002:a05:6000:1a45:: with SMTP id t5mr9744559wry.306.1640524497393; Sun, 26 Dec 2021 05:14:57 -0800 (PST) Received: from smtpclient.apple ([2a01:e34:ec28:8cb0:bdfc:aa2b:ce73:acd2]) by smtp.gmail.com with ESMTPSA id o12sm13931582wrc.69.2021.12.26.05.14.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Dec 2021 05:14:56 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\)) Subject: Re: [PATCH] Make integer output faster in libgfortran From: FX In-Reply-To: <43c60a0b-06b5-162b-bd5f-a7177cd76172@netcologne.de> Date: Sun, 26 Dec 2021 12:14:57 +0100 Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <91272BC5-B108-4DB0-929C-EE437703F10B@gmail.com> References: <28ba2e92-065e-109f-b9e2-95b4609d0f66@netcologne.de> <18EA83FD-C127-4A5B-942B-224083947F9F@gmail.com> <43c60a0b-06b5-162b-bd5f-a7177cd76172@netcologne.de> To: Thomas Koenig X-Mailer: Apple Mail (2.3693.40.0.1.81) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2021 13:15:02 -0000 Hi, > I tested this on x86_64-pc-linux-gnu with > make -k -j8 check-fortran = RUNTESTFLAGS=3D"--target_board=3Dunix'{-m32,-m64}'" > and didn't see any problems. Thanks Thomas! Pushed. > (We could also do something like that for a 32-bit system, but > that is another kettle of fish). We probably wouldn=E2=80=99t get a speed-up that big. Even on 32-bit = targets (at least common ones), the 64-bit type and its operations = (notably division) are implemented via CPU instructions, not library = calls. At this point, the output of integers is probably bound by the many = layers of indirection of libgfortran's I/O system (which are necessary = because of the rich I/O formatting allowed by the standard). Best, FX=