This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: unsupported f95 syntax


On Thu, Nov 25, 2004 at 09:59:59AM -0800, Tim Prince wrote:
> I've offered to post bugzillas on unsupported syntax, but hesitated, not 
> knowing whether these stereotypes are of any interest.

EPARSE

> 1.  vector subscript syntax, compiler reports "to do:"  (discussed 
> previously on this list)
>               a(n1:n)= b(n1:n)+c(n-ip(n1:n)+1)*d(n1:n)

PR 12366

> 2.  statement function in forall(), compiler reports as illegal function 
> call
>       f(x,y)= x*y
>           forall( i= 1:n)
>             a(i)= a(i)+f(b(i),c(i))
>             endforall
> This one looks trivial, but is commonly used, because it may be necessary 
> to have a way to switch in dprod().  Internal functions tend not to be 
> optimized as well, are relatively clumsy, and probably aren't allowed in 
> this context.

I can't locate a PR for this.

> 3.  array assignment in forall(), gfortran apparently doesn't initialize 
> the loop counter, or it gets clobbered, so it seg faults

PR 15080

> 4.  unpack() seg faults

PR 17283

> Would any of those make useful bugzilla entries?  With full 
> Levine-Callahan-Dongarra test harness, individual cases, more diagnosis? 
> Or, should they wait for some future version?

Unreported bugs won't get fixed.  Bug reports with code showing the
problem is helpful.  Even better are bug reports with patches.

-- 
Steve


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]