On Fri, Mar 2, 2012 at 11:12 AM, Paul Richard Thomas <paul.richard.tho...@gmail.com> wrote: > OK for trunk with RM agreement. Obviously, 4.5 & 4.6 are OK too.
Ok for trunk. Richard. > Thanks > > Paul > > On Fri, Mar 2, 2012 at 10:35 AM, Tobias Burnus <bur...@net-b.de> wrote: >> There is a 4.5 to 4.7 regression for those (vendor) intrinsic procedures, >> which can exists as both subroutine and as function. Example: >> >> INTRINSIC :: etime >> CALL etime(tarray, result) >> >> Here, the "etime" gets marked as attr.subroutine, but later in >> resolve_intrinsics, it is mapped to the intrinsic function "etime". But then >> the compiler complains: >> >> Error: FUNCTION attribute conflicts with SUBROUTINE attribute in 'etime' at >> (1) >> >> >> Solution: Don't search for the function, if we have a subroutine. (For some >> reasons, it works without "INTRINSIC :: etime".) >> >> Build and regtested on x86-64-linux. >> OK for the trunk - and the 4.5 to 4.6 branches? >> >> Tobias >> >> PS: I will ask for RM approval if this patch gets approved after (today's?) >> RC1 release. > > > > -- > The knack of flying is learning how to throw yourself at the ground and miss. > --Hitchhikers Guide to the Galaxy
