[Bug libfortran/116400] [15/16 Regression] Regenerated files are no longer written to the source directory

2025-05-31 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 --- Comment #16 from kargls at comcast dot net --- (In reply to kargls from comment #15) > (In reply to Francois-Xavier Coudert from comment #12) > > Created attachment 61532 [details] > > Regeneration script > > > > Attached is a shell script,

[Bug fortran/120431] SPREAD does not handle scalar argument and NCOPIES=-1 correctly

2025-05-28 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431 --- Comment #7 from kargls at comcast dot net --- Created attachment 61543 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61543&action=edit Fix for scalar source with ncopies < 0 This patch fixes the case of a scalar SOURCE and NCOPIES < 0

[Bug libfortran/116400] [15/16 Regression] Regenerated files are no longer written to the source directory

2025-05-28 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 --- Comment #15 from kargls at comcast dot net --- (In reply to Francois-Xavier Coudert from comment #12) > Created attachment 61532 [details] > Regeneration script > > Attached is a shell script, to be placed in libgfortran/, that can be run in

[Bug libfortran/116400] [15/16 Regression] Regenerated files are no longer written to the source directory

2025-05-27 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 --- Comment #8 from kargls at comcast dot net --- On 5/27/25 15:04, iains at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 > > --- Comment #6 from Iain Sandoe --- > (In reply to kargls from comment #4) >> FX, Iain

[Bug libfortran/116400] [15/16 Regression] Regenerated files are no longer written to the source directory

2025-05-27 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 --- Comment #7 from kargls at comcast dot net --- (In reply to Iain Sandoe from comment #6) > (In reply to kargls from comment #4) > > FX, Iain, > > > > Can one of you please fix this bug or revert your patch? > > It would be unfortunate to ret

[Bug libfortran/116400] [15/16 Regression] Regenerated files are no longer written to the source directory

2025-05-27 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/120431] SPREAD does not handle scalar argument and NCOPIES=-1 correctly

2025-05-27 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431 --- Comment #5 from kargls at comcast dot net --- (In reply to anlauf from comment #4) > (In reply to Jerry DeLisle from comment #3) > > My understanding is they are getting built generated in the build directory > > which is a recent bug someone

[Bug fortran/120431] SPREAD does not handle scalar argument and NCOPIES=-1 correctly

2025-05-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431 --- Comment #2 from kargls at comcast dot net --- The following diff "fixes" the problem. Or, I should say it would fix the problem if I could regenerate the c files from the m4 file. For whatever reason, --enable-maintainer-mode no longer rege

[Bug bootstrap/120438] --enable-maintainer-mode is broken

2025-05-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120438 kargls at comcast dot net changed: What|Removed |Added Resolution|--- |INVALID Status|U

[Bug bootstrap/120438] --enable-maintainer-mode is broken

2025-05-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120438 --- Comment #4 from kargls at comcast dot net --- > gmake[3]: Entering directory '/home/kargl/gcc/obj/lto-plugin' > cd ../../gcc/lto-plugin && /bin/sh /home/kargl/gcc/gcc/missing > automake-1.15 --foreign > configure.ac:4: error: your implement

[Bug bootstrap/120438] New: --enable-maintainer-mode is broken

2025-05-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120438 Bug ID: 120438 Summary: --enable-maintainer-mode is broken Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap

[Bug fortran/120431] SPREAD does not handle scalar argument and NCOPIES=-1 correctly

2025-05-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431 --- Comment #1 from kargls at comcast dot net --- (In reply to kargls from comment #0) > Consider, > > real :: arr > arr = 1 > print *, spread(arr, 1, -1) > end > Small update. The above should be handled in simplification, but curren

[Bug fortran/120431] New: SPREAD does not handle scalar argument and NCOPIES=-1 correctly

2025-05-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431 Bug ID: 120431 Summary: SPREAD does not handle scalar argument and NCOPIES=-1 correctly Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/106035] F2018 allows an IMPORT statement within the BLOCK construct.

2025-05-19 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106035 --- Comment #11 from kargls at comcast dot net --- (In reply to Paul Thomas from comment #9) > Created attachment 61467 [details] > Test vehicle for my f2018 import patch > > Hi Steve, > > Note the sections marked WRINKLE. ifx considers an asso

[Bug fortran/106035] F2018 allows an IMPORT statement within the BLOCK construct.

2025-05-19 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106035 --- Comment #10 from kargls at comcast dot net --- (In reply to Paul Thomas from comment #8) > Created attachment 61466 [details] > > As I wrote elsewhere, I should have checked if anybody else is working on > import. Apologies for treading on yo

[Bug fortran/103312] [11/12 Regression] ICE in gfc_find_component since r9-1098-g3cf89a7b992d483e

2025-05-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103312 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-10 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #27 from kargls at comcast dot net --- On 5/10/25 06:21, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 > > --- Comment #26 from anlauf at gcc dot gnu.org --- > Have you tried to move some of t

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-09 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #25 from kargls at comcast dot net --- On 5/9/25 20:22, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 > > --- Comment #24 from Jerry DeLisle --- > It is interestingly complex. As I try dif

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-09 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #23 from kargls at comcast dot net --- On 5/9/25 17:50, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 > > Jerry DeLisle changed: > > What|Removed |Adde

[Bug fortran/120131] Misleading and unnecessary error message due to range check

2025-05-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120131 --- Comment #9 from kargls at comcast dot net --- (In reply to Vladimir Terzi from comment #8) > I initially changed the status, because I assumed that my questions in > comment #2 will be ignored. > > (In reply to kargls from comment #6) > > I

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #19 from kargls at comcast dot net --- On 5/6/25 18:57, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 > > --- Comment #18 from Jerry DeLisle --- > Some fall out after the commit. This may

[Bug fortran/120140] generic type-bound procedure, defined assignment, and subarray reference

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120140 --- Comment #2 from kargls at comcast dot net --- Issue found at https://fortran-lang.discourse.group/t/defined-assignment-for-polymorphic-variable-and-vector-subscript/9666

[Bug fortran/120140] generic type-bound procedure, defined assignment, and subarray reference

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120140 kargls at comcast dot net changed: What|Removed |Added Keywords||rejects-valid --- Comment #1

[Bug fortran/120140] New: generic type-bound procedure, defined assignment, and subarray reference

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120140 Bug ID: 120140 Summary: generic type-bound procedure, defined assignment, and subarray reference Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: norma

[Bug fortran/120131] Misleading and unnecessary error message due to range check

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120131 --- Comment #6 from kargls at comcast dot net --- (In reply to Vladimir Terzi from comment #5) > After a fruitful discussion in Stack Overflow, I understand that the model > set of integers in Fortran is symmetric about zero according to the form

[Bug fortran/120131] Misleading and unnecessary error message due to range check

2025-05-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120131 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/120111] program with bad format that compiles and runs

2025-05-05 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120111 --- Comment #2 from kargls at comcast dot net --- This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88052 which you submitted. I don't have 15.1 installed, so cannot confirm whether or not the patch made it into 15.1.

[Bug fortran/120111] program with bad format that compiles and runs

2025-05-05 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120111 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-04 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #13 from kargls at comcast dot net --- On 5/4/25 16:51, kargls at comcast dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 > > --- Comment #12 from kargls at comcast dot net --- > (In reply to Jerry DeLisle from c

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-04 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #12 from kargls at comcast dot net --- (In reply to Jerry DeLisle from comment #11) > (In reply to kargls from comment #8) > > program tests_gtk_sup > >use gtk_sup > >implicit none > >type(c_ptr), target :: val > >prin

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-02 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 --- Comment #8 from kargls at comcast dot net --- (In reply to Jerry DeLisle from comment #7) > That is exactly the patch I was testing Steve. I assume that you've found that you'll need to deal with both c_ptr_1 and c_ptr_2. With the short-cir

[Bug fortran/120049] ICE when using IS_C_ASSOCIATED ()

2025-05-02 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119948] Source allocation of pure function result rejected

2025-05-02 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #18 from kargls at comcast dot net --- On 5/2/25 01:06, pault at gcc dot gnu.org wrote: > I got to thinking for once. I think that your change to primary.cc has cast > the > net a bit too wide and risks turning other kinds of interf

[Bug fortran/119948] Source allocation of pure function result rejected

2025-05-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #16 from kargls at comcast dot net --- On 5/1/25 11:55, pault at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 > > --- Comment #15 from Paul Thomas --- > (In reply to kargls from comment #14) >> HI Pau

[Bug fortran/119948] Source allocation of pure function result rejected

2025-05-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #14 from kargls at comcast dot net --- HI Paul, The difference in my pr119948_1.f90 and pr119948_2.f90 is that the former is Damian's testcase with a result-name while latter does not use result-name so the function-name is the resul

[Bug fortran/119948] Source allocation of pure function result rejected

2025-05-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #12 from kargls at comcast dot net --- On 5/1/25 07:45, pault at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 > > --- Comment #11 from Paul Thomas --- > (In reply to GCC Commits from comment #10) >> T

[Bug fortran/119986] Complex array part references are being passed incorrectly to a procedure

2025-04-29 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119986 --- Comment #5 from kargls at comcast dot net --- On 4/29/25 17:01, neil.n.carlson at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119986 > > --- Comment #4 from Neil Carlson --- > (In reply to kargls from comment #3) >>

[Bug fortran/119986] Complex array part references are being passed incorrectly to a procedure

2025-04-29 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119986 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119994] Valid specification expression in block rejected

2025-04-29 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119994 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119976] f951: ICE in compare_parameter, at fortran/interface.cc:2537

2025-04-28 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119976 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119948] Source allocation of pure function result rejected

2025-04-28 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #7 from kargls at comcast dot net --- On 4/28/25 07:30, pault at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 > > --- Comment #6 from Paul Thomas --- > (In reply to Paul Thomas from comment #5) >> Cre

[Bug fortran/119948] Source allocation of pure function result rejected

2025-04-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #3 from kargls at comcast dot net --- Created attachment 61202 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61202&action=edit fix the issues The attached patch has passed regression testing on x86_64-*-freebsd. * pri

[Bug fortran/119948] Source allocation of pure function result rejected

2025-04-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 --- Comment #2 from kargls at comcast dot net --- (In reply to Damian Rouson from comment #0) > > % gfortran -c source-allocate-pure-function-result-component.f90 > source-allocate-pure-function-result.f90:17:20: > >17 | allocate(test%i

[Bug fortran/119948] Source allocation of pure function result rejected

2025-04-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/79330] gfortran 5.4.0/6.3.0/7.0.0 misinterpret type of character literal bind(C,name=...)

2025-04-23 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79330 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net ---

[Bug fortran/119836] [15 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-23 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #20 from kargls at comcast dot net --- Jerry, thanks for getting this in gcc15.

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

2025-04-22 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114020 --- Comment #2 from kargls at comcast dot net --- (In reply to anlauf from comment #1) > (In reply to kargls from comment #0) > > Found with the Fujitsu testsuite. Reduced testcase. > > Note, if the use of ENTRY is replace with an actual > > fu

[Bug fortran/119836] [15/16 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-18 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #14 from kargls at comcast dot net --- Created attachment 61157 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61157&action=edit Patch to fix issue Here are Changelog entries for fortran/ and testsuite/. 2025-04-18 Steven G.

[Bug fortran/119836] [15/16 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-18 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #12 from kargls at comcast dot net --- On 4/17/25 23:59, pault at gcc dot gnu.org wrote: > > Is it worth reverting or fixing this before the 15-branch release? After all, > the bug made its way into the Fedora 42 release? I'll submi

[Bug fortran/119836] [15/16 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-17 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #9 from kargls at comcast dot net --- (In reply to kargls from comment #4) > + bool is_pure = e->value.function.isym > + || (e->value.function.esym > + && (e->value.function.esym->a

[Bug libgdiagnostics/119837] Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-17 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 --- Comment #9 from kargls at comcast dot net --- On 4/17/25 02:43, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 > > --- Comment #7 from Jakub Jelinek --- > I can reproduce with xterm, but the ) characte

[Bug libgdiagnostics/119837] Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 --- Comment #5 from kargls at comcast dot net --- On 4/16/25 22:01, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 > > --- Comment #4 from Andrew Pinski --- > I was looking into this and don't see COLUMN

[Bug fortran/119836] [15 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #7 from kargls at comcast dot net --- On 4/16/25 17:33, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 > > --- Comment #6 from Jerry DeLisle --- > I get one test failure: > > FAIL: gfortra

[Bug libgdiagnostics/119837] Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 --- Comment #3 from kargls at comcast dot net --- So, in my testing I use an 80-column wide xterm. The warning I see is Warning: The Hollerith constant at (1) is truncated in conversion to 'INTEGER(4' [-Wcharacter-truncation] The last parenthe

[Bug fortran/119836] [15 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #4 from kargls at comcast dot net --- All intrinsic functions are simple, and therefore pure. The following patch should fix the issue with functions. A similar fix is needed for subroutine, but only a few intrinsic subroutine are p

[Bug fortran/119836] [15 Regression] Elemental intrinsic treated as IMPURE within BLOCK within DO CONCURRENT

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836 --- Comment #3 from kargls at comcast dot net --- Well, that's weird. It appears that I'm the guilty person. 'git blame resolve.cc' leads to 7d92901c878c commit 7d92901c878c6c00ada7f9cee8825f03ad4722f1 Author: Steve Kargl Date: Sun Nov 24 18

[Bug libgdiagnostics/119837] Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 --- Comment #2 from kargls at comcast dot net --- grep %qs\" fortran/*.cc | wc -l shows that there are 102 occurrences of warning/error strings the end with a quoted string. I haven't tried to construct Fortran codes to seem if any of the othe

[Bug libgdiagnostics/119837] Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 kargls at comcast dot net changed: What|Removed |Added Component|fortran |libgdiagnostics --- Comment

[Bug fortran/119837] New: Off-by-one truncation in a warning message from gfortran with quoted string

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119837 Bug ID: 119837 Summary: Off-by-one truncation in a warning message from gfortran with quoted string Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: no

[Bug fortran/119827] Out of bounds check fails on substrings for upper bound

2025-04-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119827 --- Comment #3 from kargls at comcast dot net --- (In reply to Visagan Ravindran from comment #2) > (In reply to kargls from comment #1) > > Perhaps, a review of the Fortran standard is in order. > > > >F2023, 9.4.1 > > > >R910 substrin

[Bug fortran/119827] Out of bounds check fails on substrings for upper bound

2025-04-15 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119827 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

2025-04-14 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 --- Comment #6 from kargls at comcast dot net --- (In reply to kargls from comment #5) > (In reply to anlauf from comment #4) > > (In reply to Keith Refson from comment #3) > > > I think it probably also needs to flag up if MOLD contains an alloc

[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

2025-04-14 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 --- Comment #5 from kargls at comcast dot net --- (In reply to anlauf from comment #4) > (In reply to Keith Refson from comment #3) > > I think it probably also needs to flag up if MOLD contains an allocatable or > > pointer component too. Modif

[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

2025-04-14 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 --- Comment #2 from kargls at comcast dot net --- (In reply to kargls from comment #1) > (In reply to Keith Refson from comment #0) > > > > > I suggest at least issuing a warning to expect undefined run-time behaviour! > > > > Here's a patch h

[Bug fortran/119800] Use of Fortran TRANSFER intrinsic with argument of derived type containing allocatable causes storage aliasing

2025-04-14 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119800 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119575] ICE parsing expression with overloaded operators

2025-04-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119575 --- Comment #2 from kargls at comcast dot net --- (In reply to kargls from comment #1) > By placing line numbers on every line of the program, once cannot simply > copy and > paste the code into a file for testing. The code as written contains i

[Bug fortran/119575] ICE parsing expression with overloaded operators

2025-04-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119575 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119478] New: structure constructor is using the wrong stride

2025-03-26 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119478 Bug ID: 119478 Summary: structure constructor is using the wrong stride Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/119157] ice in gfc_enforce_clean_symbol_state, at fortran/symbol.cc:4459

2025-03-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119157 --- Comment #3 from kargls at comcast dot net --- (In reply to kargls from comment #1) > Works for me. > > What OS? > > How was gcc configured? Whoops, I take that back. I missed that you were using the -Wall option. f951: internal compiler

[Bug fortran/119157] ice in gfc_enforce_clean_symbol_state, at fortran/symbol.cc:4459

2025-03-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119157 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119136] Printing result of function that prints itself hangs

2025-03-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119136 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/119118] substring with negative start index

2025-03-04 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119118 --- Comment #2 from kargls at comcast dot net --- On 3/4/25 16:33, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119118 > > Jerry DeLisle changed: > > What|Removed |Added

[Bug fortran/119118] New: substring with negative start index

2025-03-04 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119118 Bug ID: 119118 Summary: substring with negative start index Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug fortran/108369] FM509 Fails to compile with error when using undocumented -x option

2025-02-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369 --- Comment #22 from kargls at comcast dot net --- On 2/25/25 20:28, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369 > > --- Comment #21 from Jerry DeLisle --- > (In reply to kargls from comment #20) >>

[Bug fortran/108369] FM509 Fails to compile with error when using undocumented -x option

2025-02-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369 --- Comment #20 from kargls at comcast dot net --- (In reply to Jerry DeLisle from comment #19) > > What this is doing is invoking -std=legacy for files with suffixes that > imply legacy files such as .f > > This is my first dive on the lang-spe

[Bug fortran/108680] Wrong DTIO arguments with -fdefault-integer-8

2025-02-25 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680 --- Comment #11 from kargls at comcast dot net --- On 2/25/25 12:43, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680 > > --- Comment #10 from anlauf at gcc dot gnu.org --- > (In reply to Jerry DeLisle from

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

2025-02-23 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102368 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/84386] Implicitly declared variables in BLOCK have scope of including program unit

2025-02-17 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84386 --- Comment #3 from kargls at comcast dot net --- (In reply to Thomas Koenig from comment #2) > This is fixed, already in 13.3.0. > > Commit a test case and close? Or is this already covered in the > testsuite? The test still fails for me with

[Bug fortran/84591] Compiling gfortran.dg/bind_c_usage_10.f03 with -fdefault-integer-8 gives errors

2025-02-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84591 --- Comment #7 from kargls at comcast dot net --- (In reply to kargls from comment #6) > (In reply to anlauf from comment #5) > > (In reply to kargls from comment #4) > > > (In reply to Thomas Koenig from comment #3) > > > > Resolve as invalid? >

[Bug fortran/84591] Compiling gfortran.dg/bind_c_usage_10.f03 with -fdefault-integer-8 gives errors

2025-02-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84591 --- Comment #6 from kargls at comcast dot net --- (In reply to anlauf from comment #5) > (In reply to kargls from comment #4) > > (In reply to Thomas Koenig from comment #3) > > > Resolve as invalid? > > > > IMHO. Yes. > > > > IMNSHO, -fdefault

[Bug fortran/118789] [15 Regression] ICE in gfc_add_modify_loc, at fortran/trans.cc:229

2025-02-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118789 --- Comment #7 from kargls at comcast dot net --- (In reply to Jerry DeLisle from comment #6) > Steve have you had a closer look at this one? I did watch f951 in gdb with the code in comment #3, but I could not find where to avoid an ICE. The s

[Bug fortran/84591] Compiling gfortran.dg/bind_c_usage_10.f03 with -fdefault-integer-8 gives errors

2025-02-16 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84591 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net ---

[Bug fortran/118884] [15 regression] lapack fails to compile (Error: Type mismatch at (1) passing global function ‘cslect’ declared at (2) (UNKNOWN/LOGICAL(4)))

2025-02-15 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118884 --- Comment #11 from kargls at comcast dot net --- (In reply to Thomas Koenig from comment #10) > Fixed with r15-7552-gfd00010ba21c04bddb20aef52f62de5636075067 . Thanks for the quick fix.

[Bug fortran/118884] [15 regression] lapack fails to compile (Error: Type mismatch at (1) passing global function ‘cslect’ declared at (2) (UNKNOWN/LOGICAL(4)))

2025-02-14 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118884 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/96909] ICE with nested polymorphic allocatable component

2025-02-11 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96909 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net ---

[Bug fortran/118789] [15 Regression] ICE in gfc_add_modify_loc, at fortran/trans.cc:229

2025-02-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118789 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/118783] CLASS, pointer association, and an array element of a component.

2025-02-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118783 --- Comment #1 from kargls at comcast dot net --- Created attachment 60413 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60413&action=edit scalar test case that passes testing

[Bug fortran/118783] New: CLASS, pointer association, and an array element of a component.

2025-02-07 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118783 Bug ID: 118783 Summary: CLASS, pointer association, and an array element of a component. Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug libfortran/114618] Format produces incorrect output when contains 1x, ok when uses " "

2025-02-06 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114618 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/117798] Audit intrinsic subprograms with scalar INTENT(OUT) character strings

2025-02-04 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117798 --- Comment #10 from kargls at comcast dot net --- (In reply to Thomas Koenig from comment #9) > F2023 states > > The following Fortran 2018 features might have a different interpretation > under this document. > > After an allocatable deferred

[Bug libgcc/118685] FreeBSD static executables segfault due to libgcc missing crtbeginT.o

2025-02-03 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685 --- Comment #5 from kargls at comcast dot net --- On 2/3/25 19:52, gerald at pfeifer dot com wrote: > > --- Comment #4 from Gerald Pfeifer --- > Note that with @Andreas Tobler we have a formal GCC on FreeBSD maintainer > who I am looping in, th

[Bug fortran/118735] gfortran not following deferred initialization rules for get_command_argument

2025-02-03 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118735 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/117798] Audit intrinsic subprograms with scalar INTENT(OUT) character strings

2025-02-03 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117798 --- Comment #6 from kargls at comcast dot net --- On 2/3/25 02:14, tkoenig at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117798 > > Thomas Koenig changed: > > What|Removed |Added >

[Bug fortran/118571] UTF-8 output and the A edit descriptor

2025-02-01 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118571 --- Comment #14 from kargls at comcast dot net --- (In reply to Jerry DeLisle from comment #13) > Closing as fixed. Thanks!

[Bug fortran/118710] Segmentation fault on innocuous line in sub module

2025-01-31 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118710 --- Comment #8 from kargls at comcast dot net --- I just looked at your code in bugreport2.tar.gz. It uses a parameterized derived type. PDT are broken on gfortran. Unfortunately, there is no easy fix for PDT, and it has been suggested it needs

[Bug fortran/118710] Segmentation fault on innocuous line in sub module

2025-01-31 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118710 --- Comment #5 from kargls at comcast dot net --- (In reply to Ryan Koehler from comment #4) > Created attachment 60339 [details] > Example code that throws error with this patch Thanks. I was afraid that wrong code would occur or I simply put

[Bug fortran/118710] Segmentation fault on innocuous line in sub module

2025-01-30 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118710 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug fortran/118705] Issue compiling derived types when split into submodules

2025-01-30 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118705 --- Comment #3 from kargls at comcast dot net --- (In reply to Ryan Koehler from comment #2) > Hmm that is interesting. > > That fix seemed to work. Its been a while since I read the ISO standard, but > I don't think what I sent over is out-of-s

[Bug fortran/118705] Issue compiling derived types when split into submodules

2025-01-30 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118705 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug libgcc/118685] FreeBSD static executables segfault due to libgcc missing crtbeginT.o

2025-01-28 Thread kargls at comcast dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685 kargls at comcast dot net changed: What|Removed |Added CC||gerald at gcc dot gnu.org,

  1   2   3   >