From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Jerome Huck <jeromehuck@orange.fr>
Cc: gcc-help <gcc-help@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: GCC8
Date: Mon, 25 Jun 2018 19:16:00 -0000 [thread overview]
Message-ID: <CAO9iq9HJVg_JYiu+GYfLVHYFM7mYgOyx_Ue+c_kc5WVxfS54aQ@mail.gmail.com> (raw)
In-Reply-To: <84f2ba3c-c434-e061-ebec-dde8d1b97cad@orange.fr>
On Sun, Jun 24, 2018 at 5:45 PM, Jerome Huck <jeromehuck@orange.fr> wrote:
> Private communication. If someone has clues/hints...Thanks in advance !!!
>
> Hi.
>
> I just have a new small laptop with N4200 proc. In the past I have one
> N3470.
>
> With GCC , a couple of years ago, I used the Linpack(Fortran) in single
> precision to have an idea of the proc capabilities.
>
> I attached the Fortran source code. I downloaded GCC from this web page
> see http://www.equation.com/servlet/equation.cmd?fa=fortran
>
> With the N3470, I was able to have more than 1 GigaFlops. (-O2, -O4...)
> and there was a difference when you changed the level of optimisation.
>
> I just tried it with the N4200, same result with different levels of
> optimisation, benchmark around 300 Megaflops !!!
>
> I was just expecting something a little above the N3470 !
>
> Clues/Hints?
>
> Thanks in advance.
>
> Best regards.
>
Last I heard, equation.com have (substantially) modified the GCC version
they are distributing. I recommend that you either try to recreate your
problem with a build of the upstream sources (e.g. from the mingw-w64
project), or that you contact equation.com for help with your issue with
their product.
(Added the fortran list to CC, in case other gfortran developers have
better up to date information about the equation.com builds)
--
Janne Blomqvist
parent reply other threads:[~2018-06-24 18:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <84f2ba3c-c434-e061-ebec-dde8d1b97cad@orange.fr>]
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=CAO9iq9HJVg_JYiu+GYfLVHYFM7mYgOyx_Ue+c_kc5WVxfS54aQ@mail.gmail.com \
--to=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jeromehuck@orange.fr \
/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).