[Bug fortran/57116] New: ICE for pointer assignment inside SELECT TYPE on UP entity

2013-04-29 Thread Bader at lrz dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57116 Bug #: 57116 Summary: ICE for pointer assignment inside SELECT TYPE on UP entity Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRME

[Bug fortran/57117] New: ICE for sourced allocation of a UP entity that uses the transpose intrinsic

2013-04-29 Thread Bader at lrz dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57117 Bug #: 57117 Summary: ICE for sourced allocation of a UP entity that uses the transpose intrinsic Classification: Unclassified Product: gcc Version: 4.8.0 S

[Bug libfortran/57174] New: RTE triggered by type component allocation

2013-05-05 Thread Bader at lrz dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57174 Bug #: 57174 Summary: RTE triggered by type component allocation Classification: Unclassified Product: gcc Version: fortran-dev Status: UNCONFIRMED Severity: normal

[Bug fortran/85625] New: Intenal Compiler Error for coindexed assignment

2018-05-03 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 44054 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44054&action=edit reproducer for described problem The attached Fortran file produces an I

[Bug fortran/85507] [6/7/8/9 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2258

2018-05-03 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85507 Bader at lrz dot de changed: What|Removed |Added CC||Bader at lrz dot de --- Comment

[Bug fortran/85625] Internal Compiler Error for coindexed assignment

2018-05-03 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85625 Bader at lrz dot de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution

[Bug fortran/89363] New: RANK incorrect for unallocated allocatable

2019-02-15 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45732 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45732&action=edit test code The attached program compiles without complaints using gfortran 9.

[Bug fortran/89364] New: Assumed rank object with incorrect values for shape and bounds

2019-02-15 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45734 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45734&action=edit test code The attached code compiles

[Bug fortran/89365] New: Inquiry functions for assumed rank objects fail

2019-02-15 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45735 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45735&action=edit test code The attached test code produces failures for the SHAPE, LBO

[Bug fortran/89366] New: Fails to compile BIND(C) interface with assumed-length character argument

2019-02-15 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45736 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45736&action=edit test code The extensio

[Bug fortran/89364] Assumed rank object with incorrect values for shape and bounds

2019-02-18 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89364 --- Comment #2 from Bader at lrz dot de --- (In reply to Dominique d'Humieres from comment #1) > Why do you want the shape to be [4,-1]? The Fortran 2018 standard explicitly prescribes this in 16.9.172, para 5. Regards Reinhold

[Bug fortran/89384] New: CONTIGUOUS dummy argument in BIND(C) interface incorrect when actual is non-contiguous

2019-02-18 Thread Bader at lrz dot de
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45746 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45746&action=edit test code Fortr

[Bug fortran/89385] New: Incorrect members of C descriptor for an allocatable object

2019-02-18 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45747 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45747&action=edit test code The attached test case provides

[Bug fortran/89385] Incorrect members of C descriptor for an allocatable object

2019-02-18 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89385 --- Comment #1 from Bader at lrz dot de --- Further comment: Analogous failures also happen for descriptors of assumed-shape or POINTER objects. I suggest that I re-test these when this bug is fixed and submit a separate report if still

[Bug fortran/89388] New: Component selection for assumed-size DT array

2019-02-18 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 45750 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45750&action=edit test code The attached test case, which is non-conforming (because it requir

[Bug fortran/89388] Component selection for assumed-size DT array

2019-02-18 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89388 --- Comment #1 from Bader at lrz dot de --- Actually, C1002 applies for expressions, which is not relevant for this case ... the only (non-constraint) restriction that one could (indirectly) argue to apply is 9.5.2 para2, inasmuch as the shape

[Bug fortran/89365] Inquiry functions for assumed rank objects fail

2019-02-20 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89365 --- Comment #3 from Bader at lrz dot de --- I agree with Harald's assessment. The test case as delivered by me is indeed incorrectly written for the POINTER and ALLOCATABLE cases, in both of which I believe the bounds should be taken fro

[Bug fortran/89365] Inquiry functions for assumed rank objects fail

2019-02-20 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89365 --- Comment #5 from Bader at lrz dot de --- The corrected test case passes all tests, so the PR can be closed. Sorry for the noise.

[Bug fortran/89366] Fails to compile BIND(C) interface with assumed-length character argument

2019-02-20 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366 --- Comment #2 from Bader at lrz dot de --- Fortran 2018 FDIS section 18.3.6, para 2, item 5, bullet 2: (5) any dummy argument without the VALUE attribute corresponds to a formal parameter of the prototype that is of a pointer type, and either

[Bug fortran/89366] Fails to compile BIND(C) interface with assumed-length character argument

2019-02-20 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366 --- Comment #3 from Bader at lrz dot de --- Created attachment 45771 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45771&action=edit C code to be called Added the C side function call.

[Bug fortran/89366] Fails to compile BIND(C) interface with assumed-length character argument

2019-02-20 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366 --- Comment #5 from Bader at lrz dot de --- No. The dummy argument of the procedure process_string is declared character(kind=c_char,len=*), intent(in) :: this there is no POINTER or ALLOCATABLE attribute there. Regards Reinhold

[Bug fortran/89841] New: improper descriptor information passed to C

2019-03-27 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46029 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46029&action=edit UNIX archive with test case The attached archive contains a Fortran main progra

[Bug fortran/89842] New: CFI_allocate fails to allocate object

2019-03-27 Thread Bader at lrz dot de
Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46030 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46030&action=edit UNIX archive with test case Please compile the test code from the attached arc

[Bug fortran/89843] New: CFI_section delivers incorrect result descriptor

2019-03-27 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46031 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46031&action=edit UNIX archive with test case The source code in the attached archive

[Bug fortran/89844] New: CFI_setpointer produces wrong descriptor

2019-03-27 Thread Bader at lrz dot de
Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46032 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46032&action=edit UNIX archive with test case The source code in the attached archive can be compil

[Bug fortran/89846] New: CFI_select_part creates incorrect descriptor

2019-03-27 Thread Bader at lrz dot de
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46033 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46033&action=edit UNIX archive with test case Compiling the source files in the attached archi

[Bug fortran/67744] [OOP] polymorphic associating entity is refused TBP invocation

2019-04-03 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67744 --- Comment #5 from Bader at lrz dot de --- This is still not fixed in current trunk.

[Bug fortran/90093] New: Extended C interop: optional argument incorrectly identified as PRESENT

2019-04-15 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 46166 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46166&action=edit UNIX archive with test ca

[Bug fortran/79434] New: [submodules] separate module procedure breaks encapsulation

2017-02-08 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 40698 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40698&action=edit test case The attached code (a much sim

[Bug fortran/82550] New: program using submodules fails to link

2017-10-14 Thread Bader at lrz dot de
Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 42365 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42365&action=edit reproducer The attached example implements a separate module procedure retu

[Bug fortran/67743] New: Associating entity is not auto-typed

2015-09-28 Thread Bader at lrz dot de
Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 36407 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36407&action=edit Fortran free form source for test case The attached test case generates the fo

[Bug fortran/67744] New: polymorphic associating entity is refused TBP invocation

2015-09-28 Thread Bader at lrz dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 36408 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36408&action=edit Fortran free form source for test case The a

[Bug fortran/67744] polymorphic associating entity is refused TBP invocation

2015-10-12 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67744 --- Comment #2 from Bader at lrz dot de --- The question on validity is not unjustified. The 2008 standard appears to be not fully clear on this, but the current 2015 draft has the following amended text in para 2 of section 8.1.3.3: --- The

[Bug fortran/67744] polymorphic associating entity is refused TBP invocation

2015-10-12 Thread Bader at lrz dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67744 --- Comment #3 from Bader at lrz dot de --- The question on validity is not unjustified. The 2008 standard appears to be not fully clear on this, but the current 2015 draft has the following amended text in para 2 of section 8.1.3.3: --- The

[Bug fortran/97210] New: Intrinsic function get_team() does not work

2020-09-25 Thread Bader at lrz dot de via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 49273 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49273&action=edit Test case The attached test program fails with the following error

[Bug fortran/114188] New: Overloading assignment does not invalidate intrinsic assignment

2024-03-01 Thread Bader at lrz dot de via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 57583 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57583&action=edit test case for invalid use of ass

[Bug fortran/114188] Overloading assignment does not invalidate intrinsic assignment

2024-03-01 Thread Bader at lrz dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188 --- Comment #2 from Bader at lrz dot de --- You note that > Unfortunately, the five requirements in 10.2.1.4 for defined assignment > do not say anything about argument association. Hmm, one could see this as "intentionally&

[Bug fortran/114235] New: Object undefined is specific procedure for generic overload in abstract type

2024-03-05 Thread Bader at lrz dot de via Gcc-bugs
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 57613 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57613&action=edit test case for ove