[Bug bootstrap/96492] New: : internal compiler error: Segmentation fault

2020-08-05 Thread townsend at astro dot wisc.edu
Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I'm attempting to build 10.2 from within a Docker container based on Centos 5.11, which ships with glibc 2.5 and gcc 4.1.2. (The reaso

[Bug bootstrap/96492] : internal compiler error: Segmentation fault

2020-08-06 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96492 --- Comment #2 from Rich Townsend --- (In reply to Richard Biener from comment #1) > Did GCC 10.1 work or any older version you tried to build this way in the > past? It's worked in 9.2, 9.3, and earlier releases; but not in 10.1. If I try the

[Bug bootstrap/96492] : internal compiler error: Segmentation fault

2020-08-06 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96492 --- Comment #4 from Rich Townsend --- (In reply to Jakub Jelinek from comment #3) > Can you run > gdb --args ./cc1 -quiet -fself-test=../../gcc/gcc/testsuite/selftests > /dev/null -o /dev/null > and do > run > bt > ? [user@6d6cb5609b91 gcc]$ gdb

[Bug bootstrap/96492] : internal compiler error: Segmentation fault

2020-08-08 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96492 --- Comment #5 from Rich Townsend --- So, given that gcc 4.1.2 is really ancient, I've tried building 10.2 using gcc 9.3.0 instead (but still inside the Docker container). This builds fine, and in fact I'm happy to go with this workaround. Howev

[Bug fortran/93175] New: ICE involving nested parameterized derived types

2020-01-06 Thread townsend at astro dot wisc.edu
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I get an ICE when compiling this example code (involving a PDT inside a PDT): module pdt_test_m type :: matrix (k,n) integer, kind :: k integer

[Bug fortran/56218] New: Segfault with allocatable intent(out) derived type argument having allocatable component

2013-02-05 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56218 Bug #: 56218 Summary: Segfault with allocatable intent(out) derived type argument having allocatable component Classification: Unclassified Product: gcc Version: 4.8.0

[Bug fortran/56655] New: Associate construct with OpenMP triggers ICE

2013-03-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56655 Bug #: 56655 Summary: Associate construct with OpenMP triggers ICE Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Prio

[Bug libgcc/56656] New: Suffix or operands invalid for 'movq'

2013-03-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656 Bug #: 56656 Summary: Suffix or operands invalid for 'movq' Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal P

[Bug libgcc/56656] Suffix or operands invalid for 'movq'

2013-03-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656 --- Comment #2 from Rich Townsend 2013-03-20 02:11:30 UTC --- (In reply to comment #1) > Can you try to compile it out of the src directory in another directory? I > think that is what is causing it. Could you clarify what you mean --

[Bug libgcc/56656] Suffix or operands invalid for 'movq'

2013-03-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656 --- Comment #4 from Rich Townsend 2013-03-20 04:20:56 UTC --- (In reply to comment #3) > svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_8-branch gcc-src > mkdir gcc-objdir > cd gcc-objdir > ../gcc-src/configure > make No change

[Bug bootstrap/56656] Suffix or operands invalid for 'movq'

2013-03-20 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656 --- Comment #12 from Rich Townsend 2013-03-20 12:56:53 UTC --- (In reply to comment #9) > So I guess an important question is if the "svn-fetched 4.8.0" wasn't actually > "svn-fetched trunk" instead, Uros' changes have been committed only

[Bug fortran/56655] Associate construct with OpenMP triggers ICE

2013-03-20 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56655 --- Comment #2 from Rich Townsend 2013-03-20 13:25:15 UTC --- (In reply to comment #1) > (In reply to comment #0) > > Created attachment 29692 [details] > > Test source file to reproduce the error > > > > Attempting to compile the atta

[Bug fortran/56670] New: Allocatable-length character var causes bogus warning with -Wall

2013-03-20 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56670 Bug #: 56670 Summary: Allocatable-length character var causes bogus warning with -Wall Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED

[Bug fortran/56748] New: STOP statement + array optional variable causes bogus uninitialized warning

2013-03-26 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56748 Bug #: 56748 Summary: STOP statement + array optional variable causes bogus uninitialized warning Classification: Unclassified Product: gcc Version: 4.8.0 Status: UN

[Bug fortran/50269] Wrongly rejects element of assumed-shape array in C_LOC

2013-04-01 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50269 Rich Townsend changed: What|Removed |Added CC||townsend at astro dot

[Bug fortran/50269] Wrongly rejects element of assumed-shape array in C_LOC

2013-04-01 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50269 --- Comment #6 from Rich Townsend 2013-04-01 22:24:35 UTC --- (In reply to comment #4) > FIXED on the 4.9 trunk. Are we sure? When running the code example given in comment #1, I get a segfault. Moreover, the following subroutine won

[Bug fortran/56872] New: Incorrect SUM evaluation, involving implied-do loop, with -ffrontend-optimize

2013-04-07 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56872 Bug #: 56872 Summary: Incorrect SUM evaluation, involving implied-do loop, with -ffrontend-optimize Classification: Unclassified Product: gcc Version: 4.9.0

[Bug fortran/56872] Incorrect SUM evaluation, involving implied-do loop, with -ffrontend-optimize

2013-04-07 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56872 --- Comment #1 from Rich Townsend 2013-04-08 06:02:42 UTC --- Created attachment 29821 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29821 Test program to reproduce the error

[Bug fortran/55199] New: Equivalenced variable has wrong type when used with generic member function

2012-11-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55199 Bug #: 55199 Summary: Equivalenced variable has wrong type when used with generic member function Classification: Unclassified Product: gcc Version: 4.7.3 S

[Bug fortran/55199] [OOP] Equivalenced variable has wrong type when used with generic member function

2012-11-04 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55199 --- Comment #9 from Rich Townsend 2012-11-04 18:01:53 UTC --- (In reply to comment #8) > Fixed with r193136. Closing. > > Thanks for reporting this! Hey, thanks for fixing it so quickly -- you never cease to amaze me!

[Bug fortran/47463] New: ICE in gfc_add_component_ref

2011-01-25 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47463 Summary: ICE in gfc_add_component_ref Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: fortran AssignedTo: unassig...@gcc.gn

[Bug fortran/47463] [OOP] ICE in gfc_add_component_ref

2011-01-26 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47463 --- Comment #3 from Rich Townsend 2011-01-27 04:06:10 UTC --- (In reply to comment #2) > (In reply to comment #1) > > 4.5 fails with: > > use hydro_recon > > 1 > > Internal Error at (1): > > mio_component_ref(): Component not f

[Bug fortran/47546] New: Internal error - free_pi_tree(): Unresolved fixup

2011-01-30 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 Summary: Internal error - free_pi_tree(): Unresolved fixup Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo

[Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup

2011-02-02 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #4 from Rich Townsend 2011-02-02 16:52:49 UTC --- On Feb 2, 2011, at 8:49 AM, janus at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 > > --- Comment #3 from janus at gcc dot gnu.org 2011-02-02 14:49:16 U

[Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup

2011-02-02 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #9 from Rich Townsend 2011-02-02 19:56:25 UTC --- (In reply to comment #8) > On the other hand, the failure is very elusive: Even removing the 'implicit > none' line in the module 'hydro_types' (which btw is never used) will make it >

[Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup

2011-02-02 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #15 from Rich Townsend 2011-02-03 00:09:57 UTC --- (In reply to comment #10) > (In reply to comment #9) > > Sounds like a Heisenbug -- it goes away when you look for it. Would it be > > worth > > bringing valgrind into the picture? >

[Bug fortran/47601] New: Internal Error (mio_component_ref(): Component not found) with strange behavior

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 Summary: Internal Error (mio_component_ref(): Component not found) with strange behavior Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority:

[Bug fortran/47601] Internal Error (mio_component_ref(): Component not found) with strange behavior

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #1 from Rich Townsend 2011-02-03 18:45:47 UTC --- (In reply to comment #0) > This is similar to problems I've been encountering with another code (see > pr47456). But in cutting down the attached code to find the simplest possible > t

[Bug fortran/47601] Internal Error (mio_component_ref(): Component not found) with strange behavior

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #3 from Rich Townsend 2011-02-03 19:20:12 UTC --- Created attachment 23239 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23239 Fixed Makefile Removed some broken dependencies from the original Makefile

[Bug fortran/47601] Internal Error (mio_component_ref(): Component not found) with strange behavior

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #5 from Rich Townsend 2011-02-03 21:17:29 UTC --- Created attachment 23241 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23241 Revised tar archive w/ source & Makefile Seems some stuff got left out of the tar file. Here's a new

[Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #17 from Rich Townsend 2011-02-03 22:54:34 UTC --- (In reply to comment #16) > Rich, in case this is a blocker on a real world application, you can probably > circumvent the error by not use-importing hydro_state when you use-import >

[Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup

2011-02-03 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #18 from Rich Townsend 2011-02-03 23:04:22 UTC --- (In reply to comment #8) > This is a *very* strange bug, to say the least. Here is a reduced test case: > > > module hydro_types > implicit none > end module hydro_types > > modu

[Bug fortran/47637] New: Memory leak involving derived types w/ allocatable components

2011-02-07 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47637 Summary: Memory leak involving derived types w/ allocatable components Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compo

[Bug fortran/57922] New: Memory leak with allocatable polymorphics

2013-07-17 Thread townsend at astro dot wisc.edu
Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Created attachment 30520 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30520&action=edit Example program I'm experiencing a problem with: Using built-in specs. COLLECT_GCC=/

[Bug c/57956] New: missing 'msgstr' section errors when building

2013-07-22 Thread townsend at astro dot wisc.edu
mponent: c Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu When compiling trunk on x86_64 Fedora Core 6, I encounter the following after configuring and running make: make[3]: Entering directory `/home/townsend/mesasdk-src/gcc/host-x86_64-pc-lin

[Bug c/57956] missing 'msgstr' section errors when building

2013-07-23 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57956 --- Comment #1 from Rich Townsend --- Temporary workaround: add --disable-nls to ./configure args.

[Bug fortran/53309] Unnecessary temporary array creation in subroutine call

2013-07-24 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53309 --- Comment #3 from Rich Townsend --- Thanks for the explanation about -Warray-temporaries vs. -fcheck-array-temporaries -- got it! Might be worth changing the output text from the former to something like "Warning: Array temporary might be creat

[Bug fortran/58007] [OOP] ICE in free_pi_tree(): Unresolved fixup - resolve_fixups does not fixup component of __class_bsr_Bsr_matrix

2013-09-11 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58007 Rich Townsend changed: What|Removed |Added CC||townsend at astro dot wisc.edu

[Bug fortran/53309] New: Unnecessary temporary array creation in subroutine call

2012-05-10 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53309 Bug #: 53309 Summary: Unnecessary temporary array creation in subroutine call Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED S

[Bug fortran/53544] New: Derived-type components in namelist group declaration produces error

2012-05-31 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53544 Bug #: 53544 Summary: Derived-type components in namelist group declaration produces error Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRME

[Bug fortran/53945] New: Scalar element of assumed-shape dummy array not recognized as C interoperable

2012-07-12 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53945 Bug #: 53945 Summary: Scalar element of assumed-shape dummy array not recognized as C interoperable Classification: Unclassified Product: gcc Version: 4.7.2 Status: U

[Bug fortran/52153] New: REAL128 gives extended precision, not quad precision

2012-02-07 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52153 Bug #: 52153 Summary: REAL128 gives extended precision, not quad precision Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/59589] New: Memory leak when deallocating polymorphic

2013-12-23 Thread townsend at astro dot wisc.edu
Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Created attachment 31507 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31507&action=edit Test code demonstrating leak The attached code leaks memory, as indicated by the 'ps' call.

[Bug fortran/58007] [4.7/4.9 Regression] [OOP] ICE in free_pi_tree(): Unresolved fixup - resolve_fixups does not fixup component of __class_bsr_Bsr_matrix

2013-12-23 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58007 --- Comment #11 from Rich Townsend --- #6 fails with 4.9.0 (svn rev. 206179), on both OS X and Linux.

[Bug fortran/59589] Memory leak when deallocating polymorphic

2013-12-23 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59589 --- Comment #1 from Rich Townsend --- Oops, missed out details. This is with rev. 206179, on both OS X and Linux.

[Bug fortran/59589] Memory leak when deallocating polymorphic

2013-12-23 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59589 --- Comment #3 from Rich Townsend --- (In reply to Dominique d'Humieres from comment #2) > Works for me on OS X for 4.8.2 or trunk. What command are you using? townsend@talos ~ $ gfortran -v Using built-in specs. COLLECT_GCC=/Applications/madsdk/

[Bug fortran/59589] [4.9 Regression] Memory leak when deallocating polymorphic

2013-12-24 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59589 --- Comment #10 from Rich Townsend --- (In reply to Dominique d'Humieres from comment #9) > > So it's actually a regression. > > Marking as a regression, even if I am not fully convinced. Further support from valgrind on x86_64-pc-linux-gnu: ==

[Bug fortran/91537] New: Memory leak involving nested allocatable derived types

2019-08-23 Thread townsend at astro dot wisc.edu
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 46748 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46748&action=edit Leak demonstration program The attached test

[Bug fortran/91537] Memory leak involving nested allocatable derived types

2019-08-24 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91537 --- Comment #3 from Rich Townsend --- (In reply to Thomas Koenig from comment #1) > Comment on attachment 46748 [details] > Leak demonstration program > > Here's the output on current trunk: > > 862548 > 8725

[Bug fortran/91584] New: Bogus warning from -Warray-bounds during string assignment

2019-08-28 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- The following test program produces bogus -Warray-bounds warnings at compile time: program test_bounds character(256) :: foo foo

[Bug fortran/91690] New: Slow IEEE intrinsics

2019-09-06 Thread townsend at astro dot wisc.edu
: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 46844 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46844&action=edit Demo program The intrinsics provided by the IEEE_ARITHMETIC module appear to be signif

[Bug fortran/90237] New: Bogus warning from -Wdo-subscript

2019-04-24 Thread townsend at astro dot wisc.edu
Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I'm encountering a bogus subscript-in-loop warning triggered by -Wdo-subscript Example: -- program do_subscript_bug implicit none real:: a(10) integer :: i

[Bug fortran/90238] New: Bogus warning from -Warray-bounds, triggered by zero-length character literal

2019-04-24 Thread townsend at astro dot wisc.edu
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- The zero-length character literal following example program triggers a bogus array-bounds warning: -- program

[Bug fortran/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal

2019-04-24 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238 --- Comment #1 from Rich Townsend --- An even-simpler demo: -- program test_str_2 write(*,*) '' end program test_str_2 -- Compile with -O2 -Warray-bounds gives test_str_2.f90:3:0: write(*,*) '' Warning: array subscript 1 is above arra

[Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal

2019-04-24 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238 --- Comment #3 from Rich Townsend --- (In reply to kargl from comment #2) > -Warray-bounds is a generic GCC option, and is used in the > middle end for reporting warnings. When you use this option > it does not recognize that a Fortran string is

[Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal

2019-04-24 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238 --- Comment #5 from Rich Townsend --- (In reply to Steve Kargl from comment #4) > It's certainly confusing. gfortran.info includes > -Warray-bounds as a warning option, but there is no > description for the option. Grepping the gfortran > sour

[Bug fortran/86148] parameterized type compile time error

2019-05-15 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86148 Rich Townsend changed: What|Removed |Added CC||townsend at astro dot wisc.edu

[Bug fortran/90499] New: ICE during polymorphic assignment

2019-05-15 Thread townsend at astro dot wisc.edu
Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- The test program below causes an internal compiler error, that appears to be linked to the polymorphic assignment: -- program test implicit none type f_t end type f_t

[Bug bootstrap/90558] New: '_Atomic does not name a type' error resurfaces when building with old headers on OSX Mojave

2019-05-21 Thread townsend at astro dot wisc.edu
NCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I'm running into a bug building on OSX Mojave, which seems to be tied into th

[Bug bootstrap/90558] '_Atomic does not name a type' error resurfaces when building with old headers on OSX Mojave

2019-05-21 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90558 --- Comment #2 from Rich Townsend --- (In reply to Andrew Pinski from comment #1) > Dup. > > *** This bug has been marked as a duplicate of bug 89864 *** Are you sure? The discussion in 89864 indicates that the patch to fix this bug should be i

[Bug bootstrap/90558] '_Atomic does not name a type' error resurfaces when building with old headers on OSX Mojave

2019-05-21 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90558 --- Comment #6 from Rich Townsend --- (In reply to Rich Townsend from comment #2) > (In reply to Andrew Pinski from comment #1) > > Dup. > > > > *** This bug has been marked as a duplicate of bug 89864 *** > > Are you sure? The discussion in 89

[Bug bootstrap/90558] '_Atomic does not name a type' error resurfaces when building with old headers on OSX Mojave

2019-05-21 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90558 --- Comment #7 from Rich Townsend --- (In reply to Rich Townsend from comment #2) > (In reply to Andrew Pinski from comment #1) > > Dup. > > > > *** This bug has been marked as a duplicate of bug 89864 *** > > Are you sure? The discussion in 89

[Bug fortran/86481] New: Memory leak with nested source allocations

2018-07-11 Thread townsend at astro dot wisc.edu
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 44380 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44380&action=edit Example program showing the leak I've come across a memo

[Bug fortran/86481] Memory leak with nested source allocations

2018-07-11 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86481 --- Comment #1 from Rich Townsend --- As addenda: *) I also see the problem on gfortran 8.1 *) It doesn't seem to matter whether bar_t is a subclass of foo_t. This choice was based on the code I developed the test case for, but removing the ext

[Bug fortran/86484] New: Undefined symbol when using polymorphic intrinsic assignment

2018-07-11 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I'm getting an undefined symbol at link time when compiling the following test program, which involves intrinsic polymo

[Bug other/55387] New: Build problem: malloc error in genautomata

2012-11-18 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55387 Bug #: 55387 Summary: Build problem: malloc error in genautomata Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/69268] [5 Regression] Sourced allocation calls function twice

2016-01-26 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268 --- Comment #3 from Rich Townsend --- Proposed patch appears to work in the real-world case I'm focused on. Thanks!

[Bug fortran/70705] New: Associate construct with array section causes ICE

2016-04-17 Thread townsend at astro dot wisc.edu
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 38298 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38298&action=edit Example program In the example program attached, comp

[Bug fortran/81241] New: write end of file

2017-06-28 Thread townsend at astro dot wisc.edu
: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: ---

[Bug fortran/81241] write end of file

2017-06-28 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81241 --- Comment #1 from Rich Townsend --- (Apologies for the initial blank description, my web-browser submitted before I was ready). I've recently upgraded to gfortran 7.1 from 5.3, and am seeing a large number of breakages in a significant piece o

[Bug fortran/81241] write end of file

2017-06-28 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81241 --- Comment #2 from Rich Townsend --- Aha, given that MESA is multithreaded, this may well be linked to this issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387 Certainly, running with just 1 thread seems to make things behave.

[Bug fortran/81241] write end of file

2017-06-29 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81241 --- Comment #6 from Rich Townsend --- Jim's patch for pr81195 fixes all the issues we've been experiencing -- so yes, this counts as a duplicate. Thanks to all for the quick response.

[Bug fortran/79446] New: Passing internal procedure as argument causes segfault at runtime

2017-02-09 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 40709 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40709&action=edit Example program A

[Bug fortran/79446] Passing internal procedure as argument causes segfault at runtime

2017-02-10 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79446 --- Comment #2 from Rich Townsend --- (In reply to Dominique d'Humieres from comment #1) > > Also, I don't experience the segfault on other Linux distros > > (e.g., Gentoo/3.16.5) or Mac OS. > > Confirmed on x86_64-apple-darwin16, even using an

[Bug fortran/60370] New: TRANSPOSE on rhs of allocatable array assignment gives bounds error

2014-02-28 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu The following code: program foo real, allocatable :: a(:,:) real, allocatable :: b(:,:) allocate(a(10,5)) a = 0. b = TRANSPOSE(a) end

[Bug fortran/64173] New: ICE involving derived type function pointers

2014-12-03 Thread townsend at astro dot wisc.edu
: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Created attachment 34184 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34184&action=edit Code to reproduce the crash I'm encountering an ICE when compiling the attached cod

[Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation

2014-12-15 Thread townsend at astro dot wisc.edu
: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu I'm trying to build the latest trunk (rev. 218759) on Linux. Configuring with: ./configure CC=gcc --build=x86_64-pc-linux-gnu --prefix=/root/madsdk --with-gmp=/root/madsdk --with

[Bug bootstrap/64320] Missing config.h during findcomp.cc compilation

2014-12-16 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64320 --- Comment #1 from Rich Townsend --- OK, it seems that this bug comes from building with srcdir == objdir. If I build in a separate directory, then the problem goes away. As an aside, I hadn't realized that using srcdir == objdir is generally d

[Bug fortran/56218] [OOP] Segfault with allocatable intent(out) derived type argument having allocatable component

2014-07-14 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56218 --- Comment #4 from Rich Townsend --- Seems to work fine on 4.10 (20140710).

[Bug libfortran/60324] Handle arbitrarily long path names

2014-07-14 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60324 Rich Townsend changed: What|Removed |Added CC||townsend at astro dot wisc.edu

[Bug fortran/69185] New: bounds-check gives false positive on assignment to allocatable array

2016-01-07 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 37255 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37255&action=edit Source code of

[Bug fortran/69185] bounds-check gives false positive on assignment to allocatable array

2016-01-07 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69185 --- Comment #2 from Rich Townsend --- (In reply to Dominique d'Humieres from comment #1) > It looks like a duplicate of pr52162. Unless you object I'll mark this PRas > a duplicate in the coming days. Agreed!

[Bug fortran/69268] New: Sourced allocation calls function twice

2016-01-13 Thread townsend at astro dot wisc.edu
Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 37338 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37338&action=edit Source code of program reproducing the problem The attached

[Bug fortran/47546] [OOP] Internal error - free_pi_tree(): Unresolved fixup

2011-03-15 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #19 from Rich Townsend 2011-03-16 02:29:35 UTC --- (In reply to comment #18) > (In reply to comment #8) > > This is a *very* strange bug, to say the least. Here is a reduced test case: > > > > > > module hydro_types > > implicit n

[Bug fortran/48145] New: Generic interfaces & derived types cannot share names

2011-03-15 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48145 Summary: Generic interfaces & derived types cannot share names Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assign

[Bug fortran/48939] New: ICE in code involving procedure pointers

2011-05-09 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48939 Summary: ICE in code involving procedure pointers Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassig

[Bug fortran/47601] [OOP] Internal Error: mio_component_ref(): Component not found

2011-05-26 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #12 from Rich Townsend 2011-05-26 18:05:35 UTC --- Do we have any progress in fixing this one? It's become a showstopper for me, alas! (Serves me right for starting a number of new, large projects in F2003).

[Bug fortran/47601] [OOP] Internal Error: mio_component_ref(): Component not found

2011-05-26 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #14 from Rich Townsend 2011-05-26 21:43:27 UTC --- > Fails for me on x86_64-unknown-linux-gnu with 4.5, 4.6 and 4.7. Apparently > related to type extension. I think the bug can be summarized thus: *) The error is triggered by USEing

[Bug fortran/47601] [OOP] Internal Error: mio_component_ref(): Component not found

2011-05-29 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #28 from Rich Townsend 2011-05-29 21:10:08 UTC --- (In reply to comment #27) > r174416 fixes all the test cases in this PR (except comment #11, which is > invalid). I'm glad we finally nailed this one. > > Closing as fixed. Thanks fo

[Bug fortran/49466] New: Memory leak with assignment of extended derived types

2011-06-18 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49466 Summary: Memory leak with assignment of extended derived types Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assign

[Bug fortran/49466] Memory leak with assignment of extended derived types

2011-06-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49466 --- Comment #2 from Rich Townsend 2011-06-19 15:39:28 UTC --- (In reply to comment #1) > (In reply to comment #0) > > In the attached sample code, which is a reduced test case from the full > > code, > > the assignment "as_b = as_a" leaks memory

[Bug fortran/49466] [4.6/4.7 Regression] Memory leak with assignment of extended derived types

2011-06-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49466 --- Comment #6 from Rich Townsend 2011-06-19 18:57:40 UTC --- (In reply to comment #5) > > In the first assignment b.U is allocated, in the second assignment it is not > > freed, before being allocated again. > > I don't think it should be freed

[Bug fortran/47601] [OOP] Internal Error: mio_component_ref(): Component not found

2011-06-19 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #34 from Rich Townsend 2011-06-19 21:18:47 UTC --- Thanks, Janus -- you rock! On Jun 19, 2011, at 4:16 PM, janus at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 > > --- Comment #33 from janus at gcc do

[Bug fortran/48351] [OOP] Realloc on assignment fails if parent component is CLASS

2011-07-06 Thread townsend at astro dot wisc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48351 Rich Townsend changed: What|Removed |Added CC||townsend at astro dot

[Bug fortran/72798] New: Module (.mod) file changes even when interface does not

2016-08-03 Thread townsend at astro dot wisc.edu
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 39054 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39054&action=edit Test case demonstrating problem I

[Bug fortran/72798] Module (.mod) file changes even when interface does not

2016-08-03 Thread townsend at astro dot wisc.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72798 --- Comment #2 from Rich Townsend --- Hmm, I can understand why having an internal pure attribute makes sense from an optimiser point of view. But it results in having lots of compilation cascades during debugging, which sucks. Is there a way to

[Bug fortran/99477] New: CONTIGUOUS assumed-shape dummy not working with associate construct

2021-03-08 Thread townsend at astro dot wisc.edu via Gcc-bugs
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 50335 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50335&action=edit Example program I thi

[Bug fortran/98445] New: Bogus error: derived type used as an actual argument

2020-12-25 Thread townsend at astro dot wisc.edu via Gcc-bugs
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 49844 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49844&action=edit Minimal working example I'm running into what I bel

[Bug fortran/98445] Bogus error: derived type used as an actual argument

2020-12-26 Thread townsend at astro dot wisc.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98445 --- Comment #2 from Rich Townsend --- I know it's acceptable to overload a type name with one or more functions -- from 12.4.3.4.1 of the F2008 standard, "A generic name may be the same as a derived-type name, in which case all of the procedures

[Bug fortran/98445] Bogus error: derived type used as an actual argument

2020-12-27 Thread townsend at astro dot wisc.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98445 --- Comment #3 from Rich Townsend --- OK, my code isn't valid -- it's not permitted to pass a generic procedure name as an actual argument. As such, gfortran is correct in its behavior. Happy for this one to be closed -- sorry for the false alar

  1   2   >