[Bug fortran/48894] New: generic omp_get_ancestor_thread_num(l(i)) produces incorrect output

2011-05-05 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48894 Summary: generic omp_get_ancestor_thread_num(l(i)) produces incorrect output Product: gcc Version: 4.5.3 Status: UNCONFIRMED Severity: minor Priority: P3

[Bug fortran/45430] New: segfault in OMP code with threadprivate and copyin

2010-08-27 Thread longb at cray dot com
Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: longb at cray dot com GCC build triplet: x86_64-suse-linux GCC host triplet: x86_64-suse-linux GCC target triplet: x86_64-suse-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45430

[Bug fortran/45430] segfault in OMP code with threadprivate and copyin

2010-08-27 Thread longb at cray dot com
--- Comment #1 from longb at cray dot com 2010-08-27 18:31 --- Comments from original submitter: A [deleted] user has given me the following code which fails with gcc/4.5.0. The code is OK with PGI and CCE. The problem seems to come about from the use of threadprivate in

[Bug fortran/45430] segfault in OMP code with threadprivate and copyin

2010-08-27 Thread longb at cray dot com
--- Comment #2 from longb at cray dot com 2010-08-27 18:36 --- Created an attachment (id=21579) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21579&action=view) Test case, including source files and compile script Attached tar.gz file contains the source files and the comp

[Bug fortran/46752] New: OpenMP - Seg fault for unallocated allocatable array in firstprivate clause

2010-12-01 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46752 Summary: OpenMP - Seg fault for unallocated allocatable array in firstprivate clause Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug fortran/46753] New: ICE: OpenMP - in extract_omp_for_data, at omp-low.c:335

2010-12-01 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46753 Summary: ICE: OpenMP - in extract_omp_for_data, at omp-low.c:335 Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/46752] OpenMP - Seg fault for unallocated allocatable array in firstprivate clause

2010-12-02 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46752 --- Comment #3 from Bill Long 2010-12-02 17:22:48 UTC --- Conflicting commentary from the OpenMP testers and James Beyer of the OpenMP committee: This test case is derived from OpenMP test omp3f/F03_2_9_3_4_5c.f90 . The case involves an allocata

[Bug fortran/46752] OpenMP - Seg fault for unallocated allocatable array in firstprivate clause

2010-12-02 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46752 --- Comment #5 from Bill Long 2010-12-02 18:42:53 UTC --- Reply from James: Version 3.1 of the OpenMP specification removes the offending bullet: " A variable that appears in a firstprivate clause must be definable." When the new spec is releas

[Bug fortran/46753] [4.4 Regression] ICE: OpenMP - in extract_omp_for_data, at omp-low.c:335

2010-12-09 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46753 --- Comment #7 from Bill Long 2010-12-09 10:29:19 UTC --- I am out of the office until Tuesday, December 21, 2010. Send technical questions to spsl...@cray.com.

[Bug fortran/40876] OpenMP private variable referenced in a statement function

2010-05-07 Thread longb at cray dot com
--- Comment #7 from longb at cray dot com 2010-05-07 22:06 --- The original problem reported in the Description concerned a missing error message. So, fixing the segfault (while an excellent situation) does not address the original issue. My 2 cents is this is not ready to close yet

[Bug fortran/44084] New: OpenMP - case involving tasks with implicit shared i - incorrect output

2010-05-11 Thread longb at cray dot com
ected output is no output, e.g. from Intel compiler.] -- Summary: OpenMP - case involving tasks with implicit shared i - incorrect output Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority:

[Bug fortran/44085] New: OpenMP - untied task accesses threadprivate - non-conforming but no msg

2010-05-11 Thread longb at cray dot com
accesses threadprivate - non- conforming but no msg Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lon

[Bug fortran/44036] I can't declare an external function in an OMP shared statement.

2010-05-12 Thread longb at cray dot com
--- Comment #7 from longb at cray dot com 2010-05-12 14:34 --- For what it's worth, the Cray compiler produces this message for the test code: !$OMP shared (a,n,f) ^ ftn-1473 crayftn: ERROR DP, File = test.f90, Line = 13, Column = 19 Object F must be a var

[Bug fortran/44847] New: ICE: OpenMP with Collapse clause and CYCLE stmt in loop

2010-07-06 Thread longb at cray dot com
Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: longb at cray dot com GCC build triplet: x86_64-suse-linux GCC host triplet: x86_64-suse-linux GCC target triplet: x

[Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support

2011-07-22 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383 Bill Long changed: What|Removed |Added CC||longb at cray dot com --- Comment #6 from

[Bug fortran/49693] Spurious "unused-variable" warnings for COMMON block module variables.

2011-08-12 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49693 Bill Long changed: What|Removed |Added CC||longb at cray dot com --- Comment #1 from

[Bug fortran/95644] [F2018] IEEE_FMA is missing from the IEEE_ARITHMETIC module

2021-03-03 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 --- Comment #7 from Bill Long --- Inquiry from the original site: "Does GCC provide a timeline for when they will conform to F2018?"

[Bug fortran/95037] gfortran fails to compile a simple subroutine, issues an opaque message

2020-10-18 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95037 --- Comment #4 from Bill Long --- Original submitter is interested in knowing what GCC version will have this fix.

[Bug fortran/95038] Not treating function result name as a variable.

2020-10-18 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #4 from Bill Long --- Original submitter is looking for a fix version for this issue. Any predictions?

[Bug libfortran/95104] [9/10 Regression] Segfault on a legal WAIT statement

2020-10-18 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95104 --- Comment #18 from Bill Long --- Original submitted asking about the GCC version that has / will have the fix.

[Bug fortran/95119] [9/10 Regression] CLOSE hangs when -fopenmp is specified in compilation

2020-10-18 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95119 --- Comment #12 from Bill Long --- Original submitter asking which GCC version(s) have / will have the fix.

[Bug fortran/40876] OpenMP private variable referenced in a statement function

2020-10-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876 Bill Long changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[Bug fortran/42478] [meta-bug] gfortran OpenMP bugs

2020-10-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42478 Bug 42478 depends on bug 40876, which changed state. Bug 40876 Summary: OpenMP private variable referenced in a statement function https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876 What|Removed |Added -

[Bug fortran/95038] Not treating function result name as a variable.

2020-11-23 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #5 from Bill Long --- Original submitter asking for a fixed-in version number.

[Bug fortran/97272] New: Wrong answer from MAXLOC with character arg

2020-10-02 Thread longb at cray dot com via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- Test case: > cat test.f90 program test character, allocatable :: a(:) integer(8) l, i l = 200_8 allocate (a(l)) do i = 1, l

[Bug fortran/95644] IEEE_FMA is missing from the IEEE_ARITHMETIC module

2020-10-02 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 --- Comment #2 from Bill Long --- Any update on a fix for this? (The original customer is asking.)

[Bug fortran/95640] gfortran ieee_selected_real_kind returns 10

2020-10-02 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95640 --- Comment #19 from Bill Long --- On an ia64 Intel target that does not support x87 floating point, it seems that having IEEE_SUPPORT_DATATYPE (1._10) return .true. is as error. If that is fixed, will the rest of the issue fall into place?

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2020-10-04 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #5 from Bill Long --- The original intent of adding the KIND argument was because some implementations used a 32-bit integer for the result, and it is possible for the answer to be larger than 2**31-1. Just checking to be sure that t

[Bug fortran/95644] [F2018] IEEE_FMA is missing from the IEEE_ARITHMETIC module

2020-10-05 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 --- Comment #4 from Bill Long --- The customer has nuclear weapons. They do not do "bounty". :) Cray/HPE is just the messenger. I think they would be happy with a plan for including the routine.

[Bug fortran/98699] New: Reset OMP_NESTED to true if OMP_MAX_ACTIVE_LEVELS is > 1.

2021-01-15 Thread longb at cray dot com via Gcc-bugs
mal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- The user's desire is that, for an OpenMP code, if the maximum number of active levels (OMP_MAX_ACTIVE_LEVELS) has a value greater tha

[Bug libgomp/98699] Reset OMP_NESTED to true if OMP_MAX_ACTIVE_LEVELS is > 1.

2021-01-19 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98699 --- Comment #3 from Bill Long --- Thanks, Tobias. GCC 11 should be fine. Great to see you back.

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-01-22 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #5 from Bill Long --- Is this fixed in a release version of GCC?

[Bug fortran/95644] [F2018] IEEE_FMA is missing from the IEEE_ARITHMETIC module

2021-01-22 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 --- Comment #5 from Bill Long --- Original customer is asking again...

[Bug fortran/97272] Wrong answer from MAXLOC with character arg

2021-01-22 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272 --- Comment #10 from Bill Long --- Still fails with 10.2.0. Can you say which release version will include the fix?

[Bug fortran/95640] gfortran ieee_selected_real_kind returns 10

2021-01-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95640 --- Comment #20 from Bill Long --- Original customer is asking about the status of this issue.

[Bug fortran/95038] Not treating function result name as a variable.

2021-01-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #6 from Bill Long --- Is there a released version with the fix noted in this bug?

[Bug fortran/95038] Not treating function result name as a variable.

2021-02-01 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #9 from Bill Long --- The original test is not conforming due to the missing IMPORT statement. However, the error message , which I assume is for the second non-blank line in the listing, seems odd. The standard says "If RESULT do

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #7 from Bill Long --- For our purposes, 10 will be fine.

[Bug fortran/42954] [9/10/11/12 regression] TARGET_*_CPP_BUILTINS issues with gfortran

2021-06-01 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42954 --- Comment #35 from Bill Long --- A lot of users have moved to the 10.X series of compilers, and the adventurous ones to 11.X. Will the fixes also appear in those compilers?

[Bug fortran/104252] New: OpenMP array reduction support issue

2022-01-26 Thread longb at cray dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- Created attachment 52299 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52299&action=edit Source for test case. For the attached test case source file: > gfortra

[Bug fortran/102368] New: Failure to compile program using the C_SIZEOF function in ISO_C_BINDING

2021-09-16 Thread longb at cray dot com via Gcc-bugs
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- > cat test.f90 program main use,intrinsic :: iso_c_binding implicit none character(kind=c_char, len=*), parameter :: ble

[Bug fortran/102369] New: VALUE attribute for arrays not allowed

2021-09-16 Thread longb at cray dot com via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- > cat test.f90 module mymod contains pure real function myfunc(x) integer, value, dimension(:), intent(in) :: x myfunc = x(1) end function myfunc end module mymod program main

[Bug fortran/102369] VALUE attribute for arrays not allowed

2021-09-16 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102369 --- Comment #1 from Bill Long --- I assume the cascade of error messages all originate with the first one. The combination of VALUE for an array is allowed in F08 and later versions.

[Bug demangler/102370] New: Runtime failure with allocatable component of allocatable parent and MOVE_ALLOC

2021-09-16 Thread longb at cray dot com via Gcc-bugs
Severity: normal Priority: P3 Component: demangler Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- > cat test.f90 program main implicit none type mytype real :: val integer :: idx type(mytype), allocatable :: n

[Bug fortran/102371] New: Error for type spec in FORALL statement

2021-09-16 Thread longb at cray dot com via Gcc-bugs
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- > cat test.f90 program main implicit none integer, parameter :: long = selected_int_kind(18) integer(long), parameter :: very_large = 128_long integer, allocatable, dimens

[Bug libfortran/102370] Runtime failure with allocatable component of allocatable parent and MOVE_ALLOC

2021-09-17 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102370 --- Comment #2 from Bill Long --- I've sent a question back to the original submitter. On completion, the first argument to MOVE_ALLOC is unallocated, so it does look suspicious to be printing a component of an unallocated structure. I'll upda

[Bug fortran/95038] Not treating function result name as a variable.

2022-06-10 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #10 from Bill Long --- The original issue seems fixed in 12.1. However, the wording of the ERROR message (objecting that something is not a DATA entity when it really is) could still be improved. Can we either convert this bug to th

[Bug fortran/101658] New: Bogus message for declaration of polymorphic dummy argument

2021-07-28 Thread longb at cray dot com via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: longb at cray dot com Target Milestone: --- For this code: > cat test2.f90 module test_module use, intrinsic:: iso_fortran_env, only: int32 implicit none type, abstr

[Bug fortran/104585] incorrect error for dummy arguments with both VALUE and DIMENSION attributes

2024-04-04 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104585 Bill Long changed: What|Removed |Added CC||longb at cray dot com --- Comment #2 from

[Bug fortran/78219] [F08] specifying the kind of a FORALL index in the header

2024-04-04 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78219 --- Comment #12 from Bill Long --- Has this been fixed in a more recent version of gfortran?

[Bug fortran/104585] incorrect error for dummy arguments with both VALUE and DIMENSION attributes

2024-04-10 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104585 --- Comment #4 from Bill Long --- Any prediction for this one? (I realize you still have F2018 an F2023 to get through.)

<    1   2