public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [PATCH] Make integer output faster in libgfortran
Date: Sun, 26 Dec 2021 17:15:25 +0100	[thread overview]
Message-ID: <1471f348-1829-b253-86f3-47abb9182e25@netcologne.de> (raw)
In-Reply-To: <91272BC5-B108-4DB0-929C-EE437703F10B@gmail.com>

Hi FX,


>> (We could also do something like that for a 32-bit system, but
>> that is another kettle of fish).
> 
> We probably wouldn’t 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.

I'll look at this a bit more closely and report :-)

>  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).

There are a few things we could do.  Getting a LTO-capable version
of libgfortran would be a huge step, because the compiler could
then strip out all of these layers.  The speed of

   character:: c


   write (*,'(A)', advance="no") c

could stand some improvement :-)

Regards

	Thomas

  reply	other threads:[~2021-12-26 16:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-25 13:03 FX
2021-12-25 14:35 ` Thomas Koenig
2021-12-25 14:50   ` FX
2021-12-25 22:07     ` Thomas Koenig
2021-12-26 11:14       ` FX
2021-12-26 16:15         ` Thomas Koenig [this message]
2021-12-27 21:01           ` FX

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1471f348-1829-b253-86f3-47abb9182e25@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).