[Bug fortran/33001] error with hexadecimal DATA

2007-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-06 12:11 --- DATA LARGE(1), LARGE(2) / Z'', Z'7FEF' / Error: Arithmetic overflow converting INTEGER(16) to INTEGER(4) at (1) The error message is correct: You cannot fit the nu

[Bug fortran/33002] Hexadecimal DATA incorrect

2007-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-06 12:49 --- Using REAL RMACH(5) DATA RMACH(1) / Z'0080' / is invalid Fortran 77/90/95/2003 as Fortran only allows: "If a data-stmt-constant is a boz-literal-constant, the corresponding variable s

[Bug fortran/33001] error with hexadecimal DATA

2007-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-08-06 13:06 --- > The numbers are 32-bit, so why an overflow? huge(0): 2147483647 ! biggest (positive) number fitting into integer(4) Z'': 4294967295 I would argue that 4294967295 is bigger than 21474

[Bug fortran/32985] COMMON checking: TYPE with(out) SEQUENCE/bind(C), ALLOCATABLE

2007-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-06 19:23 --- Patch for the first part. Missing: Check for default initializer. Index: resolve.c === --- resolve.c (revision 127246) +++ resolve.c (working copy

[Bug fortran/32985] COMMON checking: TYPE with(out) SEQUENCE/bind(C), ALLOCATABLE

2007-08-06 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-06 20:18 --- Besides default initializers (TODO), I also forgot about the following, to be added after the if clause of previous patch: else if (csym->ts.type == BT_DERIVED && csym-

[Bug fortran/33015] New: F66/Vendor extension: Implement support for DATA jhlf/'f'/

2007-08-07 Thread burnus at gcc dot gnu dot org
y: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33015

[Bug fortran/33015] g77/F66/vendor extension: Implement support for DATA jhlf /'f'/

2007-08-07 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-07 20:13 --- Just for completeness: This is a regression with regards to g77. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33020] New: Bind(C): c_f_pointer: Bogus? type/rank mismatch error

2007-08-07 Thread burnus at gcc dot gnu dot org
ssigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org OtherBugsDependingO 32630 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33020

[Bug fortran/33020] Bind(C): c_f_pointer: type/rank mismatch error with integer(8) SHAPE

2007-08-08 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-08 14:23 --- Some further testing shows: NAG f95 always wants to have a default kind for SHAPE in c_f_pointer though the standard allows all kinds. If I change integer(fgsl_size_t) (fgsl_size_t = c_site_t = 8) into integer(4

[Bug fortran/32902] Document integer KIND of SIZEOF()

2007-08-08 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-08 19:01 --- I still would like to have somewhere a reference to "c_size_t" of the "iso_c_binding" module as this helps the user to actually code it. It is in any case more portable than hard coding some value

[Bug fortran/33037] TRANSFER intrinsic is context sensitive

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-09 15:50 --- Could you please tell us your gfortran version? ("gfortran -v", the gcc-version line is of most interest.) Not that TRANSFER is free of bugs, but it produces here 4.3.0 20070808 (x86_64-unknown-linux-gnu

[Bug fortran/33039] Read NAMELIST: reads wrong namelist name

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-09 18:39 --- I think this is a duplicate of PR 33019. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33039

[Bug fortran/33037] TRANSFER intrinsic is context sensitive

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-09 18:54 --- > This is undefined code, when I rewrote most of the transfer code for scalars, > I > had asked what happens when the sizes did not match and everyone I asked said > it was undefined behavior. Well,

[Bug fortran/33040] New: ICE in gfc_trans_structure_assign

2007-08-09 Thread burnus at gcc dot gnu dot org
igned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33040

[Bug fortran/33001] error with hexadecimal DATA

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-08-09 21:28 --- Subject: Bug 33001 Author: burnus Date: Thu Aug 9 21:27:52 2007 New Revision: 127321 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127321 Log: 2007-08-09 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f*

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-08-09 22:03 --- Subject: Bug 32987 Author: burnus Date: Thu Aug 9 22:02:32 2007 New Revision: 127324 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127324 Log: 2007-08-09 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f*

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2007-08-09 22:08 --- FIXED for gfortran 4.3.0; gfortran now accepts the tab; it checks also at compile time for the tab character and gives either a warning (-std=gnu/legacy) or an error (-std=f95/f2003) if a tab has been found

[Bug fortran/33040] ICE in gfc_trans_structure_assign

2007-08-09 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-09 22:23 --- Some more debugging - I modified gfc_trans_structure_assign to: -- cm = expr->ts.derived->components; i = 1; for (c = expr->value.constructor; c; c = c->next, c

[Bug fortran/31538] misleading bounds check error

2007-08-10 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-08-10 09:43 --- Newly created test case. Expected: * Extend (size) should be printed for "a = f()", as NAG f95 does (I'm not sure that "different shape" is correct for the current a=b message; addition

[Bug fortran/32827] IMPORT fails for TYPE when also used in INTERFACE

2007-08-13 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2007-08-13 21:08 --- Mark really as fixed. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33066] New: "type, bind(C) t": Diagnose missing "::"

2007-08-14 Thread burnus at gcc dot gnu dot org
d(C) t": Diagnose missing "::" Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org R

[Bug fortran/22571] Reject derived types for dummy arguments declared in the subroutine unless they are SEQUENCE

2007-08-14 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-08-14 15:48 --- Note: Instead of having the SEQUENCE property, the BIND(C) attribute ("type, bind(c) :: t") suffices as well. "Two data entities have the same type if they are declared with reference to the sa

[Bug fortran/33072] New: "use mod, only: operator(.sub.)" matches any procedure "sub"

2007-08-14 Thread burnus at gcc dot gnu dot org
3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33072

[Bug fortran/31298] Uninitialized variable in f951 (in read_module) / renaming operator in USE

2007-08-14 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2007-08-14 21:16 --- (From update of attachment 13369) > strcpy (new->local_name, name); This does not make much sense for INTERFACE_INTRINSIC_OP. The problem with being able to import an operator only once is related to PR

[Bug fortran/33072] "use mod, only: operator(.sub.)" matches any procedure "sub"

2007-08-14 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-14 21:24 --- Extended example (rejects-valid + accepts-invalid): (Overlaps partially with PR31298) module a implicit none interface operator(.op.) module procedure sub end interface contains function sub(i) integer

[Bug fortran/33077] New: gfortran.dg/random_7.f90: a.out uses uninitialized memory/test failure

2007-08-15 Thread burnus at gcc dot gnu dot org
rtran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33077

[Bug libfortran/32989] GETARG intrinsic

2007-08-16 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-16 15:19 --- > Well, the gfortran doc says "Shall be of type INTEGER(4), N >= 0". This is in > contradiction with the g77 doc, which says: "Pos: INTEGER not wider than the > default kind; scalar; IN

[Bug fortran/33072] "use mod, only: operator(.sub.)" matches any procedure "sub"

2007-08-16 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-16 18:17 --- Subject: Bug 33072 Author: burnus Date: Thu Aug 16 18:17:46 2007 New Revision: 127564 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127564 Log: 2007-08-16 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33072] "use mod, only: operator(.sub.)" matches any procedure "sub"

2007-08-16 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-16 18:20 --- FIXED - but only the initially reported bug. The other I push back to PR31298. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33095] New: MAX with optional arguments gives run-time error

2007-08-16 Thread burnus at gcc dot gnu dot org
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33095

[Bug fortran/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported

2007-08-17 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2007-08-17 08:14 --- Rejecting "operator(.procedure.)" has been fixed by PR33072. Accepting multiple renames/imports of an operator ("operator(.op.), operator(.myop.)=>operator(.op.)") is fixed by the submitted p

[Bug fortran/33095] MAX with optional arguments gives run-time error

2007-08-17 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-17 13:21 --- > Oh, sh**, I didn't think about simplification. > Well, I don't see an easy way to > have error messages at runtime, so we should simply skip those. Good idea. As long as the compiler does the

[Bug fortran/33105] New: F2003: Support is_iostat_end & is_iostat_eor intrinsics

2007-08-18 Thread burnus at gcc dot gnu dot org
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org OtherBugsDependingO 20585

[Bug fortran/33106] New: Access of components of public entities of private types wrongly allowed

2007-08-18 Thread burnus at gcc dot gnu dot org
mponent: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33106

[Bug fortran/33105] F2003: Support is_iostat_end & is_iostat_eor intrinsics

2007-08-18 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-18 12:56 --- Created an attachment (id=14072) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14072&action=view) Diff for invoke.text (only) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33105

[Bug fortran/33106] Access of components of public entities of private types wrongly allowed

2007-08-19 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-19 17:50 --- > does any other standard but F95 allow the usage of private derived type > outside their defining module? I'd think that an error is called for, > regardless of the version of the standard?! Bel

[Bug fortran/33106] Access of components of public entities of private types wrongly allowed

2007-08-19 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-19 18:54 --- Fortran 2003: --- 4.5.1.1 Accessibility Types that are defined in a module or accessible in that module by use association have either the PUBLIC or PRIVATE attribute. Types for which an access-spec is

[Bug fortran/33116] New: External functions can be called as subroutine

2007-08-19 Thread burnus at gcc dot gnu dot org
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu

[Bug fortran/33117] New: Improve error message for generic interface with subroutines & functions

2007-08-19 Thread burnus at gcc dot gnu dot org
rtedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33117

[Bug fortran/33116] External functions can be called as subroutine

2007-08-19 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-20 06:02 --- Hmm. I wonder why it did not work - probably I mixed it up with PROCEDURE(REAL). -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33106] Access of components of public entities of private types wrongly allowed

2007-08-19 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-08-20 06:21 --- Richard Maine claims that also print *, code_gree is valid. Thus there needs to be only a Fortran 95 check in module. http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/6f683312292e2865/ Note

[Bug fortran/33105] F2003: Support is_iostat_end & is_iostat_eor intrinsics

2007-08-21 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-21 15:46 --- > I wasn't even aware of their existence! Me neither. I found it in the NAG f95 release notes. > I'll do it (unless you want to?), thanks for the doc patch. Go ahead. -- http://gcc.

[Bug fortran/32980] Vendor extension: Intrinsic functions (D)GAMMA, LGAMMA (ALGAMA/DLGAMA)

2007-08-21 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-21 17:06 --- Created an attachment (id=14090) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14090&action=view) invoke.texi patch Note: I did not mention "Fortran 2008" and I also did not include "LOG

[Bug fortran/32980] Vendor extension: Intrinsic functions (D)GAMMA, LGAMMA (ALGAMA/DLGAMA)

2007-08-21 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-21 17:08 --- Created an attachment (id=14091) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14091&action=view) invoke.texi patch Note: I did not mention "Fortran 2008" and I also did not include "LOG

[Bug fortran/32980] Vendor extension: Intrinsic functions (D)GAMMA, LGAMMA (ALGAMA/DLGAMA)

2007-08-21 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-08-21 19:04 --- > * Will we want a -std=f2008 separate from f2003, or do we consider f2003 an > alias for f2008 (F2008 being, after all, a minor improvement to F2003)? Who said that it will be a minor change compared to F

[Bug fortran/33141] New: Intrinsic procedures: Improve warning/error with -std=*

2007-08-21 Thread burnus at gcc dot gnu dot org
P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33141

[Bug fortran/33139] array pointer assignment gives incorrect dimensions

2007-08-21 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-22 06:36 --- Minimal example: implicit none real, TARGET :: a(0:100) real, pointer :: p(:) p => a print *, lbound(a), ubound(a) print *, lbound(p), ubound(p) end Prints: 0 100

[Bug fortran/33139] array pointer assignment gives incorrect dimensions

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-22 14:41 --- Note: for a(:) and thus also for "p=>a(:)" the lbound starts at 1 (this is somewhere hidden in "6.2.2.3 Array sections") - this part works. Partial patch. Note: This patch is incomplete as on

[Bug fortran/33149] internal compiler error: in gfc_conv_constant

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-22 17:35 --- I think the problem has been fixed meanwhile; I can reproduce it with 4.1.3 20070521 and 4.2.1 20070705, but not with 4.3.0 20070822. Using gfortran 4.3 gives the following error message: integer :: i,j,k,ndim

[Bug fortran/33149] [4.1 and 4.2 only] internal compiler error: in gfc_conv_constant

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-22 17:46 --- > The error is caused by this line of subroutine get_cand: > integer :: i,j,k,ndim=size(cl) > if it is replaced by > integer :: i,j,k,ndim > ndim=size(cl) > then the error doesn't

[Bug tree-optimization/5035] Incorrectly produces '`' might be used uninitialized in this function'

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #18 from burnus at gcc dot gnu dot org 2007-08-22 18:07 --- > so I am tempted to close this as fixed. At least PR 27289 and PR 29479 (marked as duplicate of this PR) seem still to show the bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5035

[Bug fortran/33020] Bind(C): c_f_pointer: type/rank mismatch error with integer(8) SHAPE

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-22 21:28 --- Subject: Bug 33020 Author: burnus Date: Wed Aug 22 21:28:08 2007 New Revision: 127719 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127719 Log: 2007-08-22 Christopher D. Rickett <[EMAI

[Bug fortran/33020] Bind(C): c_f_pointer: type/rank mismatch error with integer(8) SHAPE

2007-08-22 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-22 21:29 --- FIXED on the trunk. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33162] New: Type checking absent for specific names of INTRINSIC functions

2007-08-23 Thread burnus at gcc dot gnu dot org
Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33162

[Bug fortran/33139] array pointer assignment gives incorrect dimensions

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2007-08-24 15:03 --- FIXED for gfortran 4.3.0. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33139] array pointer assignment gives incorrect dimensions

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-08-24 15:04 --- I said: FIXED. -- burnus at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/33175] Testsuite: unexpected failures

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-24 15:05 --- *** This bug has been marked as a duplicate of 33174 *** -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33174] Testsuite: unexpected failures

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-24 15:05 --- *** Bug 33175 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33174

[Bug fortran/33139] array pointer assignment gives incorrect dimensions

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-08-24 15:01 --- Subject: Bug 33139 Author: burnus Date: Fri Aug 24 15:00:59 2007 New Revision: 127770 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127770 Log: 2007-08-24 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33178] New: -std=f95: SIGN with integer arguments rejected as initialization expression

2007-08-24 Thread burnus at gcc dot gnu dot org
atus: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33178

[Bug fortran/33178] -std=f95: SIGN with integer arguments rejected as initialization expression

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-24 19:26 --- Subject: Bug 33178 Author: burnus Date: Fri Aug 24 19:26:42 2007 New Revision: 127786 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127786 Log: 2007-08-24 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33178] -std=f95: SIGN with integer arguments rejected as initialization expression

2007-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-24 19:28 --- Fixed. Was a regression and kind of a typo. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33180] New: Cannot IMPORT symbols later defined in the module

2007-08-24 Thread burnus at gcc dot gnu dot org
Version: 4.3.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33180

[Bug fortran/33188] New: Fortran 2003: Type declarations without componends

2007-08-25 Thread burnus at gcc dot gnu dot org
Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33188

[Bug fortran/33189] read(blah, fmt=*) is accepted, but read(blah, '*') not.

2007-08-25 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2007-08-25 20:27 --- READ(a, '*') i I think you mix this up with * (not '*') which is no character expression but simply a single asterisk. R914 format is default-char-expr or label or

[Bug fortran/33180] Cannot IMPORT symbols later defined in the module

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-26 09:31 --- INVALID. I missed the "prior" in: "The IMPORT statement specifies that the named entities from the host scoping unit are accessible in the interface body by host association. An entity that is i

[Bug fortran/33188] Fortran 2003: Type declarations without componends

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-26 17:59 --- Subject: Bug 33188 Author: burnus Date: Sun Aug 26 17:59:34 2007 New Revision: 127808 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127808 Log: 2007-08-26 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33188] Fortran 2003: Type declarations without componends

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-26 18:00 --- FIXED in 4.3.x/trunk. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/33196] New: Generic name to non-standard procedure: Not diagnosed with -std=f95

2007-08-26 Thread burnus at gcc dot gnu dot org
gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33196

[Bug fortran/32980] Vendor extension: Intrinsic functions (D)GAMMA, LGAMMA (ALGAMA/DLGAMA)

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2007-08-26 18:11 --- Subject: Bug 32980 Author: burnus Date: Sun Aug 26 18:11:42 2007 New Revision: 127809 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127809 Log: 2007-08-26 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33197] New: Fortran 2008: gamma() and other small changes

2007-08-26 Thread burnus at gcc dot gnu dot org
8: gamma() and other small changes Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc do

[Bug fortran/32980] Vendor extension: Intrinsic functions (D)GAMMA, LGAMMA (ALGAMA/DLGAMA)

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2007-08-26 18:25 --- FIXED for the trunk/GCC 4.3.0. The Fortran 2008 bits are tracked in PR 33197. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32985] COMMON checking: TYPE with(out) SEQUENCE/bind(C), ALLOCATABLE

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2007-08-26 18:29 --- Subject: Bug 32985 Author: burnus Date: Sun Aug 26 18:29:45 2007 New Revision: 127811 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127811 Log: 2007-08-26 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33198] New: Derived type in common: Default initializer not rejected

2007-08-26 Thread burnus at gcc dot gnu dot org
Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33198

[Bug fortran/32985] COMMON checking: TYPE with(out) SEQUENCE/bind(C), ALLOCATABLE

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-08-26 18:34 --- Partially fixed. The remaining bits (default initializer) are tracked in PR33198. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32985

[Bug fortran/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #12 from burnus at gcc dot gnu dot org 2007-08-26 18:37 --- Subject: Bug 31298 Author: burnus Date: Sun Aug 26 18:37:23 2007 New Revision: 127812 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127812 Log: 2007-08-26 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/32985] COMMON checking: TYPE with(out) SEQUENCE/bind(C), ALLOCATABLE

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-08-26 18:39 --- Mark as fixed. -- burnus at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported

2007-08-26 Thread burnus at gcc dot gnu dot org
--- Comment #13 from burnus at gcc dot gnu dot org 2007-08-26 18:43 --- REMAINING: operator(generic opterator) => operator(user operator) e.g. operator(+) => operator(.myplus.) For obvious reasons the reversed is not allowed (MR&C claims that also the former is invalid, b

[Bug fortran/33202] 'NO' runtime problem with a code compiled using gfotran ... and it should !

2007-08-27 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-27 13:44 --- Segmentation fault means: The program accessed memory it was not supposed to access. There is no error if it accesses memory which is garbage but it may access. Seemingly the first it happening with g95 and ifort and

[Bug fortran/33204] New: Run-time argument check for procedures (run-time interface checking)

2007-08-27 Thread burnus at gcc dot gnu dot org
Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33204

[Bug fortran/33202] 'NO' runtime problem with a code compiled using gfotran ... and it should !

2007-08-27 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-27 13:53 --- See also: - Run-time checking, PR33204 - Whole-file checking: PR26227 - Generating .mod files for procedures which are not contained in modules or the PROGRAM: PR30658 -- http://gcc.gnu.org/bugzilla

[Bug fortran/33215] New: Bind(C): Accepts multiple entites with same (empty) binding name

2007-08-28 Thread burnus at gcc dot gnu dot org
t: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org OtherBugsDependingO 32630 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33215

[Bug fortran/33215] Bind(C): Bugs with empty "name=": Creates wrong result and accepts invalid

2007-08-28 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-28 10:04 --- The bug is actually worse as valid Fortran 2003 programs are rejected. The following program should print "5 -5". The two static global variables are not the same as their binding name is not "a"

[Bug fortran/33221] New: IMPORTing of TYPE declarations without components fails

2007-08-28 Thread burnus at gcc dot gnu dot org
igned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33221

[Bug fortran/33215] Bind(C): Bugs with empty "name=": Creates wrong result and accepts invalid

2007-08-29 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-29 13:36 --- FIXED. -- burnus at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug fortran/33215] Bind(C): Bugs with empty "name=": Creates wrong result and accepts invalid

2007-08-29 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-29 13:09 --- Subject: Bug 33215 Author: burnus Date: Wed Aug 29 13:08:55 2007 New Revision: 127898 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127898 Log: 2007-08-29 Christopher D. Rickett <[EMAI

[Bug fortran/33228] New: Accepts use-associated functions in MODULE PROCEDURE

2007-08-29 Thread burnus at gcc dot gnu dot org
Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33228

[Bug fortran/33229] New: ICE with "intrinsic" plus calling a subroutine as function

2007-08-29 Thread burnus at gcc dot gnu dot org
routine as function Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at g

[Bug fortran/33230] New: Missing check: specification function must be pure

2007-08-29 Thread burnus at gcc dot gnu dot org
g ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33230

[Bug fortran/33231] New: Reject for -std=f* calls to elementar functions where array and scalar are mixed

2007-08-29 Thread burnus at gcc dot gnu dot org
: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33231

[Bug fortran/33232] New: Diagnose comma in "read()," and "write(),"

2007-08-29 Thread burnus at gcc dot gnu dot org
"read()," and "write()," Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org Reported

[Bug fortran/33233] New: Parent and contained procedure: Wrongly treated as generic procedures

2007-08-29 Thread burnus at gcc dot gnu dot org
ned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33233

[Bug fortran/33234] New: -stf=f* and passing intrinsic function as actual argument without INTRINSIC

2007-08-29 Thread burnus at gcc dot gnu dot org
: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33234

[Bug fortran/33040] [ISO_C_BINDING] ICE in gfc_trans_structure_assign

2007-08-29 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-29 18:15 --- At least for it currently crashes already for the following reduced example; the problem seems to be the default initializer. (Another hint that this is indeed the problem: After commenting out the "if (f->

[Bug fortran/33241] ICE with parameter string arrays

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-30 08:41 --- Please attach such long examples the next time. This makes the bug report easier to read and saves one from removing all the line breaks that get added. I tried your example with NAG f95 and it reports: Error: line

[Bug fortran/33241] ICE with parameter string arrays

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-08-30 09:04 --- Forgot to mention that gfortran gives the same error as NAG f95 but only when using -std=f95 or f2003: Error: The CHARACTER elements of the array constructor at (1) must have the same length (24/32) Work around

[Bug fortran/33241] ICE with parameter string arrays

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-30 09:07 --- Created an attachment (id=14138) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14138&action=view) Testcase of comment 0 as file -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33241

[Bug fortran/33228] Accepts use-associated functions in MODULE PROCEDURE

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-30 11:44 --- I have a patch -> accept. The standard says: "C1208 (R1206) If MODULE appears in a procedure-stmt, each procedure-name in that statement shall be accessible in the current scope as a module procedure.&

[Bug fortran/33228] Accepts use-associated functions in MODULE PROCEDURE

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-30 13:45 --- Subject: Bug 33228 Author: burnus Date: Thu Aug 30 13:44:47 2007 New Revision: 127925 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127925 Log: 2007-08-30 Tobias Burnus <[EMAIL PROTECTED]&g

[Bug fortran/33228] Accepts use-associated functions in MODULE PROCEDURE

2007-08-30 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-08-30 13:47 --- FIXED. -- burnus at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

<    5   6   7   8   9   10   11   12   13   14   >