[Bug fortran/114438] Missed constraint F2023:c7108

2024-03-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 --- Comment #6 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #5) > (In reply to anlauf from comment #3) > > The same text existed in F2018, so it is not new: F2018:C7103 and Note 1. > > > > Either eve

[Bug fortran/114438] Missed constraint F2023:c7108

2024-03-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 --- Comment #5 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #3) > The same text existed in F2018, so it is not new: F2018:C7103 and Note 1. > > Either every compiler developer team misunderstood that clause, or

[Bug fortran/114438] Missed constraint F2023:c7108

2024-03-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 --- Comment #4 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #3) > The same text existed in F2018, so it is not new: F2018:C7103 and Note 1. > > Either every compiler developer team misunderstood that clause, or

[Bug fortran/114438] Missed constraint F2023:c7108

2024-03-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 --- Comment #2 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #1) > Can you be a little more explicit? > > If I extend the program as follows: > > type(params) :: p > p = params( 0.1, 2.0 )

[Bug fortran/114438] Missed constraint F2023:c7108

2024-03-22 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4

[Bug fortran/114438] New: Missed constraint F2023:c7108

2024-03-22 Thread kargl at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Created attachment 57785 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57785=edit Fortran 2023:C7108 violation Gfortran does not diagnosis F2023:C7108. C7108 (R756) If deri

[Bug fortran/105547] No further "Unclassifiable statement" after the first one if multiple syntax errors.

2024-03-19 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105547 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 CC

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

2024-03-01 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Priority|P3

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

2024-03-01 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/114141] ASSOCIATE and complex part ref when associate target is a function

2024-02-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114141 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P4 |P5 Severity|normal

[Bug fortran/114146] REPEATABLE argument of RANDOM_INIT and repeated execution of the program

2024-02-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114146 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P5 Last reconfirmed

[Bug fortran/114141] ASSOCIATE and complex part ref when associate target is a function

2024-02-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114141 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #3 from kargl

[Bug fortran/99837] ICE in parse_associate, at fortran/parse.c:4780

2024-02-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99837 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #3 from kargl

[Bug fortran/99837] ICE in parse_associate, at fortran/parse.c:4780

2024-02-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99837 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING CC

[Bug fortran/114141] New: ASSOCIATE and complex part ref when associate target is a function

2024-02-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Created attachment 57556 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57556=edit patch gfortran rejects the following c

[Bug fortran/77504] [11/12/13/14 Regression] "is used uninitialized" with allocatable string and array constructors

2024-02-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/114023] complex part%ref of complex named constant array cannot be used in an initialization expression.

2024-02-21 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114023 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #1 from kargl

[Bug fortran/114024] ICE allocate statement with source=cmp%re and z an array

2024-02-21 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114024 --- Comment #3 from kargl at gcc dot gnu.org --- Created attachment 57482 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57482=edit patch The attached patch fixes this PR. It includes a new testcase and passes regression testing.

[Bug fortran/114024] ICE allocate statement with source=cmp%re and z an array

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114024 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #2 from kargl

[Bug fortran/114024] New: ICE allocate statement with source=cmp%re and z an array

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found with the Fujitsu testsuite. The complex part%ref is a rank-1 array with dimension=3. xx should be allocated and assigned [3.45,3.45

[Bug fortran/114023] New: complex part%ref of complex named constant array cannot be used in an initialization expression.

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found with the Fujitsu testsuite. The original code led to an ICE, but the modified version here

[Bug fortran/114022] New: ICE with a complex part%ref and nested structure constructor of complex array.

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found with the Fujitsu testsuite. The complex part%ref in the first if-stmt leads to an ICE. Likely, the nested

[Bug fortran/114021] New: ICE with allocation of scalar pointer entity where SOURCE=f() with f() returning a pointer

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Note sure if this is legal Fortran, but it leads to an ICE. Reduced testcase from Fujitsu testsuite

[Bug fortran/114020] New: ENTRY and procedure pointer leads to ICE

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found with the Fujitsu testsuite. Reduced testcase. Note, if the use of ENTRY is replace with an actual function, ie., 'function kmr_fixfun() result(zz)" the code com

[Bug fortran/114019] New: allocation with source of deferred character length entity

2024-02-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found this issues with the Fujitsu testsuite. The code is reduced to the minimum required. If I had to guess, gfc_charlen for source

[Bug fortran/113997] Bogus 'Warning: Interface mismatch in global procedure' with C binding

2024-02-19 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113997 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/113883] allocatable length parameter used but is undefined

2024-02-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113883 kargl at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed

[Bug fortran/113883] allocatable length parameter used but is undefined

2024-02-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113883 --- Comment #1 from kargl at gcc dot gnu.org --- Created attachment 57389 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57389=edit patch to fix bug This is the patch and testcase. I have successfully bootstrapped and run the Fort

[Bug fortran/113883] New: allocatable length parameter used but is undefined

2024-02-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- All, I stumbled across the following issue with my code. Consider, ! { dg-do compile } ! { dg-options "-Werror -Wall" } module foo contains

[Bug sanitizer/113881] New: Multiple testsuite failures with gfortran on FreeBSD

2024-02-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone: --- % gmake bootstrap

[Bug fortran/113866] ice in generic_simplify_COND_EXPR

2024-02-10 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113866 kargl at gcc dot gnu.org changed: What|Removed |Added Last reconfirmed||2024-02-10 Ever

[Bug fortran/113845] ice in gfc_get_array_ss

2024-02-09 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845 --- Comment #3 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #2) > (In reply to kargl from comment #1) > > Thanks. Reduce test case. > > > > subroutine test_adjustl(x) > > character(*) :: x(10

[Bug fortran/113845] ice in gfc_get_array_ss

2024-02-09 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845 --- Comment #2 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #1) > Thanks. Reduce test case. > > subroutine test_adjustl(x) > character(*) :: x(100) > call bar(adjustl(x)) > end subroutine Forcing gf

[Bug fortran/113845] ice in gfc_get_array_ss

2024-02-09 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed

[Bug fortran/113823] ice in gfc_get_element_type, at fortran/trans-types.cc:1286

2024-02-08 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823 --- Comment #3 from kargl at gcc dot gnu.org --- (In reply to David Binderman from comment #2) > (In reply to kargl from comment #1) > > (In reply to David Binderman from comment #0) > > > > > > This is the second ic

[Bug fortran/113823] ice in gfc_get_element_type, at fortran/trans-types.cc:1286

2024-02-08 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823 kargl at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1 Status

[Bug fortran/113671] Passing allocatable character(:) slices with negative stride: invalid memory access / segfault

2024-01-30 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113671 kargl at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1 CC

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2024-01-21 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #15 from kargl at gcc dot gnu.org --- (In reply to Steve Kargl from comment #14) > On Sun, Jan 21, 2024 at 09:52:39PM +, anlauf at gcc dot gnu.org wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 > &g

[Bug fortran/57360] Implement a warning for implied save

2024-01-21 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360 --- Comment #7 from kargl at gcc dot gnu.org --- Upon some additional thinking, I wonder how useful this will be compared to the possible volume of warning messages from modern Fortran. Consider this code: module foo integer :: j = 2 type

[Bug fortran/57360] Implement a warning for implied save

2024-01-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2024-01-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 kargl at gcc dot gnu.org changed: What|Removed |Added Attachment #56949|0 |1 is obsolete

[Bug fortran/113412] ATAN(Y,X) does not check arguments and generates wrong error message.

2024-01-16 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412 --- Comment #3 from kargl at gcc dot gnu.org --- Created attachment 57109 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57109=edit patch The attached patch has been regtested. There were no regression.

[Bug fortran/113412] ATAN(Y,X) does not check arguments and generates wrong error message.

2024-01-16 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412 --- Comment #2 from kargl at gcc dot gnu.org --- With the patch at the end of this message and this source code, program foo integer(8) x real(8) y, z x = 1 y = x z = atan(y,x) print *, z end I get % gfcx -c a.f90 a.f90:6

[Bug fortran/113412] ATAN(Y,X) does not check arguments and generates wrong error message.

2024-01-16 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412 --- Comment #1 from kargl at gcc dot gnu.org --- Ugh. This seems to be by design. The error message Error: Too many arguments in call to ‘atan’ at (1) is queued by intrinsic.cc(sort_actual) and appears to take precedence over an error

[Bug fortran/113413] ATAND(Y,X) is unsupported

2024-01-15 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113413 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug fortran/113413] New: ATAND(Y,X) is unsupported

2024-01-15 Thread kargl at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Fortran 2023 added ATAND(X) and ATAND(Y,X). The former is supported. The latter is unsupported. Consider. program main real(4) x, y x = 1. y = x print*, atand(y,x), atan2d(y,x

[Bug fortran/113412] ATAN(Y,X) does not check arguments and generates wrong error message.

2024-01-15 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug fortran/113412] New: ATAN(Y,X) does not check arguments and generates wrong error message.

2024-01-15 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Fortran 2008 added the misguided form ATAN(Y,X) where Y could be missing. However, if Y is present, then X is required to have

[Bug libfortran/113313] execute_command_line hangs at run time

2024-01-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #5 from kargl

[Bug libfortran/113313] execute_command_line hangs at run time

2024-01-10 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/113305] ICE with do concurrent and ivdep

2024-01-10 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113305 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/113254] Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 --- Comment #3 from kargl at gcc dot gnu.org --- (In reply to mecej4 from comment #2) > Created attachment 57001 [details] > Program source that is handled correctly when -fallow-invalid-boz is > specified Correctly? It is not

[Bug fortran/113254] Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug libfortran/113223] NAMELIST internal write missing leading blank character

2024-01-04 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223 --- Comment #4 from kargl at gcc dot gnu.org --- (In reply to Jerry DeLisle from comment #3) > Created attachment 56990 [details] > Suggested patch including affected test cases > > Regression tested OK. Three test cases affected

[Bug libfortran/113223] NAMELIST internal write missing leading blank character

2024-01-03 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223 kargl at gcc dot gnu.org changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug libfortran/113223] NAMELIST internal write missing leading blank character

2024-01-03 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4

[Bug libfortran/113223] New: NAMELIST internal write missing leading blank character

2024-01-03 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Found at https://github.com/llvm/llvm-project/issues/76798 Program test_namelist_blank Integer :: i,j Character(300) ::s Namelist

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-29 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #9 from kargl at gcc dot gnu.org --- Current patch is incomplete as it fails to scalarize. It seems I need to remember how to register the new intrinsic subprograms in trans-intrinsics.cc.

[Bug fortran/113165] Code containing more than one type declaration for a variable results in confusing error messages from compiler

2023-12-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113165 --- Comment #2 from kargl at gcc dot gnu.org --- With the attached example code and the patch at the end of this message, gfortran can be changes to identify both lines of code. Fixing the run-on errors when -fimplicit-none is used is left

[Bug fortran/113165] Code containing more than one type declaration for a variable results in confusing error messages from compiler

2023-12-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113165 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P5 CC

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #8 from kargl at gcc dot gnu.org --- Created attachment 56956 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56956=edit git diff cannot find trigpi.c (updated file) The new file tries to deal with a system with REAL(4), REA

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #7 from kargl at gcc dot gnu.org --- Created attachment 56955 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56955=edit test program for inverse functions The attach program tests the inverse functions, e.g., acospi, for

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-27 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #6 from kargl at gcc dot gnu.org --- In reflecting on the possibility of an OS lacking support for REAL(10) but having a REAL(16), the mapping of types into C are likely REAL(4) <--> float, REAL(8) <--> double,

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #4 from kargl at gcc dot gnu.org --- Created attachment 56953 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56953=edit test program

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #3 from kargl at gcc dot gnu.org --- Created attachment 56952 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56952=edit file that git cannot find Put in libgfortran/intrinsics

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #2 from kargl at gcc dot gnu.org --- Created attachment 56951 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56951=edit file that git cannot find Put file in libgfortran/intrinsics

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2023-12-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #1 from kargl at gcc dot gnu.org --- Created attachment 56950 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56950=edit new file that git cannot diff Put file in libgfortran/intrinsics.

[Bug fortran/113152] New: Fortran 2023 half-cycle trigonometric functions

2023-12-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Created attachment 56949 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56949=edit patch with implementation The attach patch implements the half-cy

[Bug fortran/113128] Wrong implied-do with optimizations

2023-12-24 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113128 kargl at gcc dot gnu.org changed: What|Removed |Added Last reconfirmed||2023-12-24 Known

[Bug fortran/112873] F2023 degree trig functions

2023-12-08 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873 --- Comment #9 from kargl at gcc dot gnu.org --- I have updated the diff. I don't know have ChangeLog works under git. Here's what I have written. * gcc/fortran/gfortran.texi: Remove the "Extended math intrinsics" node. It

[Bug fortran/112873] F2023 degree trig functions

2023-12-08 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873 kargl at gcc dot gnu.org changed: What|Removed |Added Attachment #56810|0 |1 is obsolete

[Bug fortran/112873] F2023 degree trig functions

2023-12-05 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4

[Bug fortran/112873] F2023 degree trig functions

2023-12-05 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873 --- Comment #1 from kargl at gcc dot gnu.org --- Possible ChangeLog (although I don't know the git world requirements). * intrinsic.cc(add_functions): Update the standard that the various degree trigonometric functions have been described

[Bug fortran/112873] New: F2023 degree trig functions

2023-12-05 Thread kargl at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- Created attachment 56810 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56810=edit * intrinsic.cc(add_functions): Update the standard that the various degree trigonometric functi

[Bug libfortran/112364] calloc used incorrectly

2023-11-03 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4

[Bug libfortran/112364] calloc used incorrectly

2023-11-03 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/30409] [fortran] missed optimization with pure function arguments

2023-10-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30409 --- Comment #12 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #11) > (In reply to kargl from comment #10) > > (In reply to anlauf from comment #8) > > > which is equivalent to > > > >

[Bug fortran/30409] [fortran] missed optimization with pure function arguments

2023-10-23 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30409 --- Comment #10 from kargl at gcc dot gnu.org --- (In reply to anlauf from comment #8) > The suggested optimization needs to take into account that the evaluation > of the temporary expression might trap, or that allocatable var

[Bug fortran/30409] [fortran] missed optimization with pure function arguments

2023-10-22 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30409 --- Comment #7 from kargl at gcc dot gnu.org --- The attached testcase use xmin and xmax uninitialized. After setting xmin = 0 and xmax = 1 and adding z(1) to the print statements to prevent the inner loop from being optimized away, I see

[Bug fortran/111880] [9/10/11/12/13] False positive warning of obsolescent COMMON block with Fortran submodule

2023-10-19 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111880 kargl at gcc dot gnu.org changed: What|Removed |Added Severity|normal |enhancement

[Bug fortran/111851] f951: Segmentation fault at gfc_delete_symtree

2023-10-18 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111851 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/111853] f951: Segmentation fault at gfc_expression_rank

2023-10-17 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111853 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/111218] Conflict in BIND(C) INTERFACEs in two Modules leads to ICE.

2023-10-13 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218 --- Comment #7 from kargl at gcc dot gnu.org --- An alternative patch that allows the original code to compile is diff --git a/gcc/fortran/symbol.cc b/gcc/fortran/symbol.cc index a6078bc608a..34eb3a65e8f 100644 --- a/gcc/fortran/symbol.cc +++ b

[Bug fortran/111218] Conflict in BIND(C) INTERFACEs in two Modules leads to ICE.

2023-10-13 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 --- Comment #6 from kargl

[Bug fortran/111218] Conflict in BIND(C) INTERFACEs in two Modules leads to ICE.

2023-10-13 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218 --- Comment #5 from kargl at gcc dot gnu.org --- Interesting bug. If one puts a break point ... 0x75917d gfc_format_decoder /home/toon/compilers/gcc/gcc/fortran/error.cc:1078 0x2153e1f pp_format(pretty_printer*, text_info

[Bug fortran/107716] Getting negative values with NINT when using doubleprecision values in range on i386

2023-09-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107716 --- Comment #4 from kargl at gcc dot gnu.org --- What the heck does "RESOLVED MOVED"?

[Bug fortran/111341] Elemental operator on zero-sized array seg-faults

2023-09-09 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111341 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/99711] Crash when reading an allocated character array in namelist

2023-08-31 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 kargl at gcc dot gnu.org changed: What|Removed |Added Known to work||12.2.0, 14.0

[Bug fortran/111218] Conflict in BIND(C) INTERFACEs in two Modules leads to ICE.

2023-08-28 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/109684] compiling failure: complaining about a final subroutine of a type being not PURE (while it is indeed PURE)

2023-08-08 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684 --- Comment #14 from kargl at gcc dot gnu.org --- (In reply to Paul Thomas from comment #13) > (In reply to Steve Kargl from comment #12) > > On Mon, Aug 07, 2023 at 10:04:54PM +0000, kargl at gcc dot gnu.org wrote: > > > >

[Bug fortran/109684] compiling failure: complaining about a final subroutine of a type being not PURE (while it is indeed PURE)

2023-08-07 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable

2023-08-02 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88286 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/110825] TYPE(*) dummy argument to generate an unused hidden argument

2023-07-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Priority|P3

[Bug fortran/110825] New: TYPE(*) dummy argument to generate an unused hidden argument

2023-07-26 Thread kargl at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kargl at gcc dot gnu.org Target Milestone: --- The was pointed out in Fortran Discourse, https://fortran-lang.discourse.group/t/strange-behaviour-when-using-type-and-character

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

2023-07-24 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/110725] [13/14 Regression] internal compiler error: in expand_expr_real_1, at expr.cc:10897

2023-07-19 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725 kargl at gcc dot gnu.org changed: What|Removed |Added Known to fail||14.0 Known to work

[Bug fortran/110725] [13/14 Regression,openmp] internal compiler error: in expand_expr_real_1, at expr.cc:10897

2023-07-18 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725 kargl at gcc dot gnu.org changed: What|Removed |Added Summary|[13/14 Regression] internal |[13/14 Regression,openmp

[Bug fortran/110644] Error in gfc_format_decoder

2023-07-12 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug fortran/110629] Bug in assignment of derived type with deferred length character component

2023-07-11 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110629 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

  1   2   3   4   5   6   7   8   9   10   >