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
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
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
: 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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85625
Bader at lrz dot de changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
: 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.
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
: 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
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
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
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
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
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
: 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
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
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
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.
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
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.
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
: 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
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
: 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
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
: 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
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.
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
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
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
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
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
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
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
: 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
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
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&
: 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
38 matches
Mail list logo