From: Richard Biener <richard.guenther@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
Florian Weimer <fw@deneb.enyo.de>,
Jakub Jelinek <jakub@redhat.com>,
szabolcs.nagy@arm.com,
Janne Blomqvist <blomqvist.janne@gmail.com>,
nd@arm.com, GCC Development <gcc@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
sellcey@cavium.com
Subject: Re: libmvec in gcc to have vector math in fortran
Date: Mon, 18 Jun 2018 11:10:00 -0000 [thread overview]
Message-ID: <CAFiYyc3yVLbwhGobHQ=QqAnx4Y7_7Grz3k8S_mGHn032EwjbKA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1806152058060.27276@digraph.polyomino.org.uk>
On Fri, Jun 15, 2018 at 10:59 PM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Fri, 15 Jun 2018, Thomas Koenig wrote:
>
> > Hi Richard,
> >
> > > First and foremost we need a syntax that actually works for the
> > > Fortran frontend and a way to automatically include this special
> > > header / module.
> >
> > I can imagine parsing the relevant headers while compiling gfortran
> > and generating C code from it, which could then be #included in the
> > compiler source code. It should be possible to extend mathbuiltins.def
> > that way.
>
> The libmvec functions present depend on the multilib (for example, glibc
> only currently supports them for x86_64, not for 32-bit x86). Given this
> multilib dependence, parsing the glibc headers when building the compiler
> itself is probably not a sensible option.
I'm thinking of sth like the C stdc-predef.h header which is always included
by the compiler. So it needs to be sth parseable by gfortran which means
it needs to be a module or sth equivalent to a fortran include file.
GCC supports -include on the command-line, gfortran does not and it
could also support sth like -use FOO to import module FOO. The rest could
be then done by specs processing (or similar to the stdc-predef.h via
a fortran specific target hook).
Richard.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-18 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 10:14 Szabolcs Nagy
2018-04-10 10:22 ` Janne Blomqvist
2018-04-10 11:35 ` Szabolcs Nagy
2018-04-10 12:55 ` Jakub Jelinek
2018-04-10 13:26 ` Richard Biener
2018-04-10 13:42 ` Jakub Jelinek
2018-04-10 13:27 ` Richard Biener
2018-04-10 13:35 ` Richard Biener
2018-04-18 8:41 ` Szabolcs Nagy
2018-04-18 8:57 ` Richard Biener
2018-06-14 22:41 ` Richard Biener
2018-06-15 8:39 ` Florian Weimer
2018-06-15 8:40 ` Szabolcs Nagy
2018-06-15 9:08 ` Richard Biener
2018-06-15 8:41 ` Richard Biener
2018-06-15 9:33 ` Florian Weimer
2018-06-15 11:39 ` Richard Biener
2018-06-15 20:59 ` Thomas Koenig
2018-06-15 22:41 ` Joseph Myers
2018-06-18 11:10 ` Richard Biener [this message]
2018-06-18 16:02 ` Joseph Myers
2018-06-18 16:22 ` Richard Biener
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='CAFiYyc3yVLbwhGobHQ=QqAnx4Y7_7Grz3k8S_mGHn032EwjbKA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nd@arm.com \
--cc=sellcey@cavium.com \
--cc=szabolcs.nagy@arm.com \
--cc=tkoenig@netcologne.de \
/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).