This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: how to enable vector intrinsic functions in fortran frontend
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Tobias Burnus <burnus at net-b dot de>
- Cc: Sa Liu <SALIU at de dot ibm dot com>, Andrew Pinski <pinskia at gmail dot com>, fortran at gcc dot gnu dot org, Tobias Schl?ter <tobias dot schlueter at physik dot uni-muenchen dot de>, Ulrich Weigand <Ulrich dot Weigand at de dot ibm dot com>
- Date: Mon, 22 Oct 2007 11:12:20 -0700
- Subject: Re: how to enable vector intrinsic functions in fortran frontend
- References: <OF0C105F5F.34887096-ONC125737C.0052395C-C125737C.005CFC32@de.ibm.com> <471CE4E2.8060302@net-b.de>
On Mon, Oct 22, 2007 at 07:58:58PM +0200, Tobias Burnus wrote:
> Sa Liu wrote:
> > I thought of adding them to the gfc namespace by a
> > function, say add_vmx_intrinsics, which does the similar work as
> > add_functions does in intrinsic.c. Is this somthing that Fortran frontend
> > would accept? Any better ideas to avoid mixing up Fortran generic stuff
> > and target specific functions?
> >
> I think this would be ok - as would be in principle using
> add_functions() with if(flag) { "#include ..." }. The problem I see is
> only how to do the argument checking or simplification or ... without
> duplicating too many code (from e.g. check.c) and without adding target
> specific stuff to all these files.
>
Don't forget symbol versioning. Sa Liu would also need to add
the symbols to gfortran.map.
--
Steve