[Bug fortran/97571] long parsing phase for simple array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97571 --- Comment #10 from Steve Kargl --- On Tue, Apr 27, 2021 at 06:03:16PM +, molah at ucar dot edu wrote: > I would expect a compiler must do a reasonable job to compile correct Fortran > code in a reasonable amount of time. The response for

[Bug fortran/69360] loop optimization produces invalid code when a common array has dimension 1 in some files

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69360 --- Comment #7 from Steve Kargl --- On Thu, Apr 22, 2021 at 10:20:54PM +, johnnorthall263 at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69360 > > --- Comment #6 from John Northall --- > It's deliberate! I think

[Bug fortran/100149] Seg fault passing to CHARACTER(*), DIMENSION(*), INTENT(IN), OPTIONAL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100149 --- Comment #4 from Steve Kargl --- On Wed, Apr 21, 2021 at 03:48:24PM +, brtnfld at hdfgroup dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100149 > > --- Comment #3 from Scot Breitenfeld --- > For future reference,

[Bug fortran/63797] Bogus ambiguous reference to 'sqrt'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63797 --- Comment #7 from Steve Kargl --- On Wed, Apr 14, 2021 at 08:43:50PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63797 > > --- Comment #6 from anlauf at gcc dot gnu.org --- > Steve, can you give an

[Bug fortran/63797] Bogus ambiguous reference to 'sqrt'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63797 --- Comment #5 from Steve Kargl --- On Tue, Apr 13, 2021 at 08:49:35PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63797 > > --- Comment #4 from anlauf at gcc dot gnu.org --- > The following patch

[Bug fortran/99840] [9/10/11 Regression] ICE in gfc_simplify_matmul, at fortran/simplify.c:4777

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99840 --- Comment #6 from Steve Kargl --- On Wed, Mar 31, 2021 at 08:51:57PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99840 > > --- Comment #5 from anlauf at gcc dot gnu.org --- > OK, now I see it.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 --- Comment #15 from Steve Kargl --- On Fri, Mar 26, 2021 at 01:47:28AM +, jvdelisle at gcc dot gnu.org wrote: > --- Comment #12 from Jerry DeLisle --- > This is interesting, compiling with the -g option for debugging. > > Running a test

[Bug libfortran/99740] floating point exception in rand() in gfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99740 --- Comment #4 from Steve Kargl --- On Thu, Mar 25, 2021 at 12:52:53PM +, pvoytas at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99740 > > --- Comment #3 from Paul A. Voytas --- > I see what you mean--if i test for

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 --- Comment #10 from Steve Kargl --- On Wed, Mar 24, 2021 at 05:35:31AM +, sgk at troutmask dot apl.washington.edu wrote: > > What does -ftree-dump-original show? I wonder if gfortran is doing a > re-allocation on assignment when it

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 --- Comment #9 from Steve Kargl --- On Wed, Mar 24, 2021 at 02:41:08AM +, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 > > --- Comment #7 from Jerry DeLisle --- > Digging further within

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 --- Comment #5 from Steve Kargl --- On Tue, Mar 23, 2021 at 02:41:27AM +, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711 > > --- Comment #4 from Jerry DeLisle --- > Setting the character length in

[Bug fortran/99561] gfortran reports an error for a truncation that is permitted by the standard

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99561 --- Comment #3 from Steve Kargl --- On Fri, Mar 12, 2021 at 06:39:49PM +, kargl at gcc dot gnu.org wrote: > --- Comment #1 from kargl at gcc dot gnu.org --- > (In reply to Michal Paszta from comment #0) > > In this line of code: > > > >

[Bug fortran/99506] internal compiler error: in record_reference, at cgraphbuild.c:64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 --- Comment #8 from Steve Kargl --- On Wed, Mar 10, 2021 at 10:59:39PM +, sgk at troutmask dot apl.washington.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 > > --- Comment #7 from Steve Kargl --- > On Wed, Mar 10, 2021 at

[Bug fortran/99506] internal compiler error: in record_reference, at cgraphbuild.c:64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 --- Comment #7 from Steve Kargl --- On Wed, Mar 10, 2021 at 10:22:45PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 > > --- Comment #6 from anlauf at gcc dot gnu.org --- > (In reply to Richard

[Bug fortran/99506] internal compiler error: in record_reference, at cgraphbuild.c:64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 --- Comment #5 from Steve Kargl --- On Wed, Mar 10, 2021 at 08:39:19AM +, rguenth at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506 > > --- Comment #4 from Richard Biener --- > This is a frontend issue, the FE

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 --- Comment #11 from Steve Kargl --- On Thu, Mar 04, 2021 at 02:22:46AM +, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644 > > --- Comment #10 from Jerry DeLisle --- > It is very likely that the gcc

[Bug fortran/99256] ICE in variable_check, at fortran/check.c:1012

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99256 --- Comment #2 from Steve Kargl --- On Thu, Feb 25, 2021 at 06:40:13PM +, kargl at gcc dot gnu.org wrote: > > In check_variable(), looking at gfc_current_intrinsic_arg[n]->actual, > there is locus information. there is *no* locus info.

[Bug libfortran/98301] random_init() is broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98301 --- Comment #7 from Steve Kargl --- On Mon, Feb 22, 2021 at 06:57:03PM +, sgk at troutmask dot apl.washington.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98301 > > --- Comment #6 from Steve Kargl --- > On Mon, Feb 22, 2021 at

[Bug libfortran/98301] random_init() is broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98301 --- Comment #6 from Steve Kargl --- On Mon, Feb 22, 2021 at 04:36:50AM +, jvdelisle at gcc dot gnu.org wrote: > > --- Comment #5 from Jerry DeLisle --- > Steve, if you think this does it. I will get it ready to commit for you. Does > it

[Bug fortran/99061] [10/11 Regression] ICE in gfc_conv_intrinsic_atan2d, at fortran/trans-intrinsic.c:4728

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99061 --- Comment #4 from Steve Kargl --- Neither Gerhard's original code nor my patch fixed other ICEs. Here's a test program for x86 systems. program p implicit none real(4) :: a1, e1 = 1.e-6 real(8) :: b1, e2 = 1.e-10 real(10) ::

[Bug fortran/99061] [10/11 Regression] ICE in gfc_conv_intrinsic_atan2d, at fortran/trans-intrinsic.c:4728

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99061 --- Comment #2 from Steve Kargl --- On Wed, Feb 10, 2021 at 06:03:56PM +, kargl at gcc dot gnu.org wrote: > diff --git a/gcc/fortran/trans-intrinsic.c b/gcc/fortran/trans-intrinsic.c > index 5c9258c65c3..0cf0aa56811 100644 > ---

[Bug fortran/98948] unexpected error in procedure pointer initialization or assignment with intrinsic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98948 --- Comment #2 from Steve Kargl --- On Wed, Feb 03, 2021 at 07:00:10AM +, kargl at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98948 > > kargl at gcc dot gnu.org changed: > >What|Removed

[Bug fortran/98883] Module variable not initialized with -finit-real

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98883 --- Comment #3 from Steve Kargl --- On Fri, Jan 29, 2021 at 06:55:16PM +, kargl at gcc dot gnu.org wrote: > > --- Comment #2 from kargl at gcc dot gnu.org --- > This bug report should be closed. > > Please read the description of option

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #12 from Steve Kargl --- On Sat, Jan 16, 2021 at 11:20:20PM +, Bahram.shahrooz at uc dot edu wrote: > > Do you've any suggestions for how to trace the source > of error so I can fix the code? > Not really. I suppose old

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #10 from Steve Kargl --- On Sat, Jan 16, 2021 at 04:48:09AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #9 from Bahram.shahrooz at uc dot edu --- > Yes, thank you

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #8 from Steve Kargl --- On Fri, Jan 15, 2021 at 05:21:22PM -0800, Steve Kargl wrote: > > You're using undefined variables. > I little more debugging, read(5,*) estrt,esfinal,eincr if(eincr.gt.0)

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #7 from Steve Kargl --- On Sat, Jan 16, 2021 at 12:51:38AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #6 from Bahram.shahrooz at uc dot edu --- > I get wrong

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #5 from Steve Kargl --- On Sat, Jan 16, 2021 at 12:41:56AM +, Bahram.shahrooz at uc dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 > > --- Comment #4 from Bahram.shahrooz at uc dot edu --- > I compiled with

[Bug fortran/98577] Wrong "count_rate" values with int32 and real32 if the "count" argument is int64.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 --- Comment #19 from Steve Kargl --- On Fri, Jan 08, 2021 at 06:43:20PM +, mehdi.chinoune at hotmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 > > --- Comment #17 from Chinoune --- > Once I reported a bug to

[Bug fortran/98577] Wrong "count_rate" values with int32 and real32 if the "count" argument is int64.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 --- Comment #18 from Steve Kargl --- On Fri, Jan 08, 2021 at 06:43:20PM +, mehdi.chinoune at hotmail dot com wrote: > > I concluded that is a waste of time arguing with him. > Did you run the test program from my last comment?

[Bug fortran/98577] Wrong "count_rate" values with int32 and real32 if the "count" argument is int64.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 --- Comment #8 from Steve Kargl --- On Thu, Jan 07, 2021 at 06:49:07PM +, mehdi.chinoune at hotmail dot com wrote: > > I am not asking for advice here, I reported a bug with its reproducer. What bug? > It is not your concern what kind of

[Bug fortran/98577] Wrong "count_rate" values with int32 and real32 if the "count" argument is int64.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 --- Comment #5 from Steve Kargl --- On Thu, Jan 07, 2021 at 05:28:15PM +, mehdi.chinoune at hotmail dot com wrote: > There is no mention of your claims in the standard: > I know what the standard says. > Fortran 2018: > COUNT (optional)

[Bug fortran/98517] gfortran segfault on character array initialization from parameter value since r8-5900-g266404a8d62b99ab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98517 --- Comment #4 from Steve Kargl --- On Tue, Jan 05, 2021 at 09:19:51PM +, emr-gnu at hev dot psu.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98517 > > --- Comment #3 from Eric Reischer --- > Confirm the attached patch

[Bug fortran/98490] Unexpected out of bounds in array constructor with implied do loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 --- Comment #7 from Steve Kargl --- On Sat, Jan 02, 2021 at 04:12:27AM +, jvdelisle at charter dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 > > --- Comment #5 from Jerry DeLisle --- > Patch regresses several test

[Bug fortran/96986] [8/9/10/11 Regression] Explicit interface required: volatile argument for ENTRY subroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 --- Comment #7 from Steve Kargl --- On Sat, Jan 02, 2021 at 07:53:17PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 > > --- Comment #6 from anlauf at gcc dot gnu.org --- > (In reply to kargl from

[Bug fortran/98490] Unexpected out of bounds in array constructor with implied do loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 --- Comment #6 from Steve Kargl --- On Sat, Jan 02, 2021 at 04:12:27AM +, jvdelisle at charter dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 > > --- Comment #5 from Jerry DeLisle --- > Patch regresses several test

[Bug fortran/98458] ICE in gfc_conv_array_initializer due to array expressions within implied do-loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98458 --- Comment #8 from Steve Kargl --- On Wed, Dec 30, 2020 at 01:40:22PM +, pault at gcc dot gnu.org wrote: > --- Comment #7 from Paul Thomas --- > (In reply to Steve Kargl from comment #6) > > Hi Steve, > > I didn't check for any new

[Bug fortran/98458] PRINT the array constructed from implied do-loop throw ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98458 --- Comment #6 from Steve Kargl --- On Wed, Dec 30, 2020 at 12:52:03AM +, xiao@compiler-dev.com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98458 > > --- Comment #5 from xiao@compiler-dev.com --- > (In reply to Paul

[Bug fortran/98454] Apparent wrong initialization in function result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98454 --- Comment #8 from Steve Kargl --- On Sun, Dec 27, 2020 at 10:15:56PM +, ffadrique at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98454 > > --- Comment #6 from Fran Martinez Fadrique --- > I have raised the issue

[Bug fortran/98433] double free detected in tcache 2, after merge of structures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98433 --- Comment #3 from Steve Kargl --- On Wed, Dec 23, 2020 at 11:29:47PM +, guez at lmd dot ens.fr wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98433 > > --- Comment #2 from Lionel GUEZ --- > Sure, the issue goes away if you specify

[Bug fortran/92065] [8/9/10/11 Regression] internal compiler error: in expand_expr_real_1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065 --- Comment #11 from Steve Kargl --- On Sun, Dec 20, 2020 at 05:24:53AM +, gtoth at umich dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065 > > --- Comment #10 from Gabor --- > Good to know that gfortran has come to an

[Bug fortran/92065] [8/9/10/11 Regression] internal compiler error: in expand_expr_real_1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065 --- Comment #9 from Steve Kargl --- On Sat, Dec 19, 2020 at 11:35:24PM +, gtoth at umich dot edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065 > > > Apparently this bug was reported years ago, and it was not fixed. There was

[Bug fortran/98284] ICE in get_array_index

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98284 --- Comment #3 from Steve Kargl --- On Tue, Dec 15, 2020 at 09:01:15PM +, anlauf at gcc dot gnu.org wrote: > --- Comment #2 from anlauf at gcc dot gnu.org --- > Steve, > > https://gcc.gnu.org/pipermail/fortran/2020-December/055427.html > >

[Bug fortran/98253] Conflicting random_seed/random_init results

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98253 --- Comment #9 from Steve Kargl --- On Sat, Dec 12, 2020 at 11:55:41PM +, damian at sourceryinstitute dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98253 > > Damian Rouson changed: > >What|Removed

[Bug fortran/98022] [9/10/11 Regression] ICE in gfc_assign_data_value, at fortran/data.c:468 since r9-3803-ga5fbc2f36a291cbe

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98022 --- Comment #9 from Steve Kargl --- On Sat, Dec 12, 2020 at 05:54:43PM +, pault at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98022 > > --- Comment #8 from Paul Thomas --- > The example that you give shows that

[Bug fortran/98022] [9/10/11 Regression] ICE in gfc_assign_data_value, at fortran/data.c:468 since r9-3803-ga5fbc2f36a291cbe

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98022 --- Comment #7 from Steve Kargl --- On Sat, Dec 12, 2020 at 04:02:54PM +, pault at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98022 > > --- Comment #6 from Paul Thomas --- > (In reply to kargl from comment #4) >

[Bug fortran/98201] CSQRT function gives bad resuts at runtime

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201 --- Comment #16 from Steve Kargl --- On Wed, Dec 09, 2020 at 01:24:20PM +, dpozar at ecs dot umass.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201 > > --- Comment #15 from dpozar at ecs dot umass.edu --- > attached is the

[Bug fortran/98201] CSQRT function gives bad resuts at runtime

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201 --- Comment #14 from Steve Kargl --- On Wed, Dec 09, 2020 at 12:28:49AM +, dpozar at ecs dot umass.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201 > > --- Comment #13 from dpozar at ecs dot umass.edu --- > Ok, I have

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #17 from Steve Kargl --- On Wed, Oct 07, 2020 at 07:19:18AM +, sch...@linux-m68k.org wrote: > > --- Comment #16 from Andreas Schwab --- > On powerpc64: > > FAIL: gfortran.dg/pr96711.f90 -O0 (internal compiler error) > FAIL:

[Bug fortran/97224] [8/9/10/11 Regression] SPECCPU 2006 Gamess fails to build after g:e5a76af3a2f3324efc60b4b2778ffb29d5c377bc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97224 --- Comment #6 from Steve Kargl --- On Mon, Sep 28, 2020 at 09:48:13AM +, tnfchris at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97224 > > Bug ID: 97224 >Summary: [8/9/10/11 Regression]

<    1   2   3