hooking a new intrinsic subroutine?

[Steve Kargl]

On Sun, Apr 18, 2004 at 08:34:30PM +0100, Paul Brook wrote:
> On Sunday 18 April 2004 20:26, Steve Kargl wrote:
> > > System_clock should already work properly (actually it's &rate, bit I
> > > assume that's a typo). Use -fdump-tree-original to see exactly what is
> > > being generated.
> >
> > kargl[205] gfortran -static system_clock.f90
> > /var/tmp/cch50HhN.o: In function `MAIN__':
> > /var/tmp/cch50HhN.o(.text+0x16): undefined reference to
> > `_gfortran_system_clock' /var/tmp/cch50HhN.o(.text+0x15c): undefined
> > reference to `_gfortran_system_clock' /var/tmp/cch50HhN.o(.text+0x24b):
> > undefined reference to `_gfortran_system_clock' collect2: ld returned 1
> > exit status
> 
> Ah, I menant the compiler side, not the library side!

I have a first crack at a library routine.  My original question
was how do I hook up my library routine to libgfortran?  Obviously,
I was not clear.  My routine is in libgfortran/intrinsics/system_clock.c.
I modified libgfortran/Makefile.am, but am stuck at this point.
My attempt at autoconf/automake cause unwanted damaged to my gcc tree.

> 
> > Aren't the NULL's sufficient to imply a 0 length?
> 
> A procedures always have a fixed number and type of arguments at the ABI 
> level, so we still need to pass the character lengths. The actual value 
> passed is unimportant.

Okay, I see what you mean.  I have a library routine for this too.

-- 
Steve