[Bug fortran/56174] Wrongly accepts "INTEGER :: b = HUGE(b)"

2019-01-29 Thread dominiq at lps dot ens.fr 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56174

Dominique d'Humieres  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Dominique d'Humieres  ---
Duplicate of pr35040.

*** This bug has been marked as a duplicate of bug 35040 ***

[Bug fortran/56174] Wrongly accepts "INTEGER :: b = HUGE(b)"

2014-01-07 Thread dominiq at lps dot ens.fr 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56174

Dominique d'Humieres  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2014-01-07
 Ever confirmed|0   |1

--- Comment #2 from Dominique d'Humieres  ---
Still present at r206385.

[Bug fortran/56174] Wrongly accepts "INTEGER :: b = HUGE(b)"

2013-02-01 Thread mikael at gcc dot gnu.org 

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56174

Mikael Morin  changed:

   What|Removed |Added

 CC||mikael at gcc dot gnu.org

--- Comment #1 from Mikael Morin  2013-02-01 
22:58:49 UTC ---
(In reply to comment #0)
> Using
>   INTEGER, PARAMETER :: a(2) = (/ 1, 2 /), b = HUGE(b)
> is invalid per the arguments given below.

[...]
> 
> "If a constant expression includes a specification inquiry that depends
> on a type parameter or an array bound of an entity specified in the
> same specication-part, the type parameter or array bound shall be
> specified in a prior specification of the specification-part. 
> 
One could argue that the kind parameter is specified at the end of INTEGER,
thus outside the entity-decl. ;-)
We should allow this;  there is no ambiguity.


I think there were other bugs dealing with self-recursive specification.  I
could only find pr47915, which is loosely related.