public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: 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: Fri, 15 Jun 2018 17:06:00 -0000	[thread overview]
Message-ID: <CAFiYyc2deefNfFDBqid6_n8V=J75MUUV8TqgZTJ+RUPjsG+Y5Q@mail.gmail.com> (raw)
In-Reply-To: <8736xo1kon.fsf@mid.deneb.enyo.de>

On Fri, Jun 15, 2018 at 11:08 AM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * Richard Biener:
>
> > That said, good to see some glibc folks jump in on this thread.
> > I'd like to see glibc provide a fortran intrinsic header advertising
> > the libmvec routines it has.  We probably do need some gfortran
> > adjustments here but I think that glibc advertising is better than
> > hard-coding lists into GCC (like we do for some targets with
> > their -mveclibabi= option).
>
> The advantage of putting into GCC is that it will work irrespective of
> the installed glibc header version, so if we get this going:
>
>   <https://sourceware.org/ml/libc-alpha/2018-05/msg00501.html>
>
> you could use libmvec along with really old glibcs (probably as far
> back as 2.12, maybe even older).

Well, ok - I obviously meant bundling the header with libmvec, not with
glibc (which currently is the same).

Putting it into GCC means that you have mismatches in both directions.

I was also considering to somehow auto-generate a header based
on what the C headers advertise at GCC install time.
[or put a C parser into the fortran frontend, eh...]

> But then we might into a different direction altogether.
>
> Another question is wheter the Fortran header can be generated by
> something like -fdump-ada-spec, so that we don't have to maintain it
> separately from the C header.

Sure, see above - I think that's possible and it doesn't have to be as
complicated as -fdump-ada-spec.  Instead a simple script in your
favorite language will do the job.

First and foremost we need a syntax that actually works for the
Fortran frontend and a way to automatically include this special
header / module.

Richard.

  reply	other threads:[~2018-06-15  9:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  9:45 Szabolcs Nagy
2018-04-10 10:14 ` Janne Blomqvist
2018-04-10 10:22   ` Szabolcs Nagy
2018-04-10 10:30     ` Jakub Jelinek
2018-04-10 12:55       ` Richard Biener
2018-04-10 13:07         ` Jakub Jelinek
2018-04-10 13:26           ` Richard Biener
2018-04-10 13:27           ` Richard Biener
2018-04-17 13:55             ` Szabolcs Nagy
2018-04-18  8:41               ` Richard Biener
2018-06-14 11:51           ` Richard Biener
2018-06-15  8:40             ` Florian Weimer
2018-06-15  8:41               ` Szabolcs Nagy
2018-06-15  9:22                 ` Richard Biener
2018-06-15  9:08               ` Richard Biener
2018-06-15  9:33                 ` Florian Weimer
2018-06-15 17:06                   ` Richard Biener [this message]
2018-06-16  0:04                     ` Thomas Koenig
2018-06-16 10:35                       ` Joseph Myers
2018-06-18 15:06                         ` Richard Biener
2018-06-19  9:16                           ` Joseph Myers
2018-06-19 17:00                             ` 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='CAFiYyc2deefNfFDBqid6_n8V=J75MUUV8TqgZTJ+RUPjsG+Y5Q@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=nd@arm.com \
    --cc=sellcey@cavium.com \
    --cc=szabolcs.nagy@arm.com \
    /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).