[Bug fortran/39945] -fopenmp causes runtime crash on assigning reasonably large array

2009-04-28 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #5 from KnowlesPJ at Cardiff dot ac dot uk 2009-04-28 14:53 --- O, now I see my stupidity, as for some reason ulimit -s is set to a pathetic 8192k. I am sorry to have troubled you folks with this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39945

[Bug fortran/39945] -fopenmp causes runtime crash on assigning reasonably large array

2009-04-28 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #2 from KnowlesPJ at Cardiff dot ac dot uk 2009-04-28 14:32 --- $ gfortran -v Using built-in specs. Target: i386-apple-darwin9.2.2 Configured with: ../configure --prefix=/opt/gcc --with-languages=c,fortran Thread model: posix gcc version 4.4.0 20080424 (experimental) (GCC

[Bug fortran/39945] -fopenmp causes runtime crash on assigning reasonably large array

2009-04-28 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2009-04-28 14:30 --- Created an attachment (id=17774) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17774&action=view) sample source code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39945

[Bug fortran/39945] New: -fopenmp causes runtime crash on assigning reasonably large array

2009-04-28 Thread KnowlesPJ at Cardiff dot ac dot uk
Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC build triplet: i386-apple-darwin9.2.2 GCC host triplet: i386-apple-darwin9.2.2 GCC target

[Bug fortran/39594] [4.4/4.5 Regression] compiler falls over in gfc_get_symbol_decl

2009-04-02 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #12 from KnowlesPJ at Cardiff dot ac dot uk 2009-04-02 19:49 --- It's a pleasure, and also amazing to see you folks work so quickly on this. The context for the report is our large code (http://www.molpro.net) which hopefully now for the first time will build correctly

[Bug fortran/39594] compiler falls over in gfc_get_symbol_decl

2009-03-31 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #3 from KnowlesPJ at Cardiff dot ac dot uk 2009-03-31 10:12 --- My apologies that I did not do some reduction, which of course I could have easily done. I was merely following the guidelines at http://gcc.gnu.org/bugs.html which says lots of things, but does not mention

[Bug fortran/39595] gfortran falls over in optimization

2009-03-31 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2009-03-31 08:24 --- Created an attachment (id=17567) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17567&action=view) source and includes that demonstrate the problem -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39595

[Bug fortran/39595] New: gfortran falls over in optimization

2009-03-31 Thread KnowlesPJ at Cardiff dot ac dot uk
dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC build triplet: i386-apple-darwin8.10.1 GCC host triplet: i386-apple-darwin8.10.1 GCC target triplet: i386-apple-darwin8.10.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39595

[Bug fortran/39594] compiler falls over in gfc_get_symbol_decl

2009-03-31 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2009-03-31 08:13 --- Created an attachment (id=17566) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17566&action=view) tarball containing source file and its includes -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39594

[Bug fortran/39594] New: compiler falls over in gfc_get_symbol_decl

2009-03-31 Thread KnowlesPJ at Cardiff dot ac dot uk
Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC build triplet: i386-apple-darwin8.10.1 GCC host triplet: i386-apple-

[Bug fortran/35892] gfortran lost memory blocks

2008-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #22 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-25 08:10 --- Yes, this was the silver bullet. With Using built-in specs. Target: i386-apple-darwin9.2.2 Configured with: ../configure --prefix=/opt/gcc Thread model: posix gcc version 4.4.0 20080424 (experimental) (GCC

[Bug fortran/35892] gfortran lost memory blocks

2008-04-24 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #19 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-24 09:34 --- As the originator of this report, I just wanted to add a context comment in case it is helpful. This construction (common declared both in the module and in subroutines (contained or external)) is horrible

[Bug fortran/35892] gfortran dies on file containing module and common

2008-04-09 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-09 17:24 --- Created an attachment (id=15458) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15458&action=view) Fortran source code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35892

[Bug fortran/35892] New: gfortran dies on file containing module and common

2008-04-09 Thread KnowlesPJ at Cardiff dot ac dot uk
NFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC host triplet: i386-apple-darwin9.2.2 GCC target triplet: i386-apple-darwin9.2.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35892

[Bug fortran/32155] Unresolved external __gfortran_os_error in program that manipulates strings

2007-05-31 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #4 from KnowlesPJ at Cardiff dot ac dot uk 2007-05-31 11:58 --- The compiler was downloaded from the link in http://hpc.sourceforge.net/ . -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32155

[Bug fortran/32155] Unresolved external __gfortran_os_error in program that manipulates strings

2007-05-30 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2007-05-30 13:42 --- Created an attachment (id=13633) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13633&action=view) Failing program -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32155

[Bug fortran/32155] New: Unresolved external __gfortran_os_error in program that manipulates strings

2007-05-30 Thread KnowlesPJ at Cardiff dot ac dot uk
ram that manipulates strings Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardif

[Bug fortran/31725] overwriting of neighbouring character array

2007-04-27 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #3 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-27 16:13 --- I don't agree with this analysis, as ll is certainly defined in char3.f as attached - ll=len(s) Please try with the program exactly as supplied! Yes, you are right, this function is the same as len_trim bu

[Bug fortran/31725] overwriting of neighbouring character array

2007-04-27 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #1 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-27 10:34 --- Created an attachment (id=13455) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13455&action=view) failing program -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31725

[Bug fortran/31725] New: overwriting of neighbouring character array

2007-04-27 Thread KnowlesPJ at Cardiff dot ac dot uk
Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC build triplet: i386-apple-darwin8.9.1 GCC host triplet: i38

[Bug fortran/31696] -malign-double trashes fortran format

2007-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #5 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-25 22:46 --- I guess I walk away from you guys at this point. You need to think carefully about the fortran standard, which does not define any abi whatsoever (unfortunately). The fortran programmer is not supposed to think

[Bug fortran/31696] -malign-double trashes fortran format

2007-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #2 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-25 16:47 --- I don't understand your response, or the assumptions that might be behind it. The program is standard fortran that compiles without warning, and I cannot see why I would not want doubles aligned at 64 bi

[Bug fortran/31696] New: -malign-double trashes fortran format

2007-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC build triplet: i386-apple-darwin8.9.1 GCC host triplet: i386-apple-darwin8.9.1 GCC target triplet: i386-apple