[Bug fortran/20248] gfortran: intrinsics and std=f95, inconsistency with other compilers

2006-05-05 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #13 from sgk at troutmask dot apl dot washington dot edu 2006-05-05 14:25 --- Subject: Re: gfortran: intrinsics and std=f95, inconsistency with other compilers On Fri, May 05, 2006 at 07:09:37AM -, anlauf at gmx dot de wrote: > > > --- Comment #12 from

[Bug fortran/20248] gfortran: intrinsics and std=f95, inconsistency with other compilers

2006-05-05 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #14 from sgk at troutmask dot apl dot washington dot edu 2006-05-05 17:09 --- Subject: Re: gfortran: intrinsics and std=f95, inconsistency with other compilers On Fri, May 05, 2006 at 07:09:37AM -, anlauf at gmx dot de wrote: > > Any chance that "-std=f95

[Bug fortran/27452] gfortran support for non-standard sind,cosd and friends intrinsics

2006-05-06 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2006-05-06 13:38 --- Subject: Re: gfortran support for non-standard sind,cosd and friends intrinsics On Sat, May 06, 2006 at 06:32:01AM -, deji_aking at yahoo dot ca wrote: > > > --- Commen

[Bug fortran/26119] ICE on transpose with specific compiler option

2006-05-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2006-05-08 17:48 --- Subject: Re: ICE on transpose with specific compiler option On Mon, May 08, 2006 at 04:35:25AM -, iguchi at coral dot t dot u-tokyo dot ac dot jp wrote: > > I believe that this bug

[Bug fortran/27553] Testsuite ICE with -Wunused-labels

2006-05-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #2 from sgk at troutmask dot apl dot washington dot edu 2006-05-11 19:23 --- Subject: Re: Testsuite ICE with -Wunused-labels On Thu, May 11, 2006 at 06:46:22PM -, fxcoudert at gcc dot gnu dot org wrote: > The ICE is due to -Wunused-labels. We try to issue a warn

[Bug libfortran/26564] ../.././libgfortran/mk-kinds-h.sh: Unknown type

2006-05-20 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #19 from sgk at troutmask dot apl dot washington dot edu 2006-05-20 16:54 --- Subject: Re: ../.././libgfortran/mk-kinds-h.sh: Unknown type On Sat, May 20, 2006 at 04:24:25PM -, prlw1 at cam dot ac dot uk wrote: > > > --- Comment #18 from prlw1 at cam d

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-05-27 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #20 from sgk at troutmask dot apl dot washington dot edu 2006-05-27 19:24 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sat, May 27, 2006 at 07:11:01PM -, tkoenig at gcc dot gnu dot org wrote: > > > tkoenig at gcc dot gnu dot or

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-05-27 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #22 from sgk at troutmask dot apl dot washington dot edu 2006-05-27 20:28 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sat, May 27, 2006 at 08:24:31PM -, Thomas dot Koenig at online dot de wrote: > > Do you know which version? We should mark

[Bug fortran/27954] ICE on garbage in DATA statement

2006-06-12 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2006-06-12 23:04 --- Subject: Re: ICE on garbage in DATA statement On Mon, Jun 12, 2006 at 03:32:15PM -, reichelt at gcc dot gnu dot org wrote: >- Comment #4 from reichelt at gcc dot gnu dot org 2006-06

[Bug fortran/27954] ICE on garbage in DATA statement

2006-06-12 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-06-13 00:35 --- Subject: Re: ICE on garbage in DATA statement On Mon, Jun 12, 2006 at 11:26:16PM -, reichelt at gcc dot gnu dot org wrote: > > I can reproduce the bug also on i686-pc-linux-gnu.

[Bug fortran/27954] ICE on garbage in DATA statement

2006-06-12 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2006-06-13 00:56 --- Subject: Re: ICE on garbage in DATA statement On Mon, Jun 12, 2006 at 05:34:52PM -0700, Steve Kargl wrote: > On Mon, Jun 12, 2006 at 11:26:16PM -, reichelt at gcc dot gnu dot org >

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-07-03 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #26 from sgk at troutmask dot apl dot washington dot edu 2006-07-03 17:17 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Mon, Jul 03, 2006 at 04:41:30PM -, jvdelisle at gcc dot gnu dot org wrote: > > FSEEK should be straightforward (ha ha)

[Bug fortran/27698] subroutine _foo draws "unclassifiable statement" instead of a useful error.

2006-07-05 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2006-07-05 17:35 --- Subject: Re: subroutine _foo draws "unclassifiable statement" instead of a useful error. On Wed, Jul 05, 2006 at 05:19:44PM -, aldot at gcc dot gnu dot org wrote: > > >

[Bug fortran/28276] EXPONENT() broken for real constants

2006-07-17 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2006-07-17 18:11 --- Subject: Re: EXPONENT() broken for real constants On Mon, Jul 17, 2006 at 05:54:46PM -, tobias dot burnus at physik dot fu-berlin dot de wrote: > > I see the same problem for real(8) a

[Bug libgomp/38724] Segfault caused by derived-type with allocatable component in private clause

2009-01-04 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2009-01-05 02:32 --- Subject: Re: Segfault caused by derived-type with allocatable component in private clause On Sun, Jan 04, 2009 at 09:31:20PM -, jakub at gcc dot gnu dot org wrote: > > --- Comm

[Bug fortran/38763] [4.3/4.4 Regression] Yet another TRANSFER ICE

2009-01-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2009-01-08 17:23 --- Subject: Re: [4.3/4.4 Regression] Yet another TRANSFER ICE On Thu, Jan 08, 2009 at 04:42:52PM -, pault at gcc dot gnu dot org wrote: > gfc_target_encode_expr has no means to deal w

[Bug fortran/38823] Diagnose and treat (-2.0)**2.0 properly

2009-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2009-01-13 19:43 --- Subject: Re: New: Diagnose and treat (-2.0)**2.0 properly On Tue, Jan 13, 2009 at 11:08:40AM -, burnus at gcc dot gnu dot org wrote: > > Fortran 2003 in the second sentence of the

[Bug fortran/38823] Diagnose and treat (-2.0)**2.0 properly

2009-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2009-01-13 19:44 --- Subject: Re: Diagnose and treat (-2.0)**2.0 properly On Tue, Jan 13, 2009 at 11:28:05AM -, pinskia at gmail dot com wrote: > > -2.0^1.9 will be a complex number. Maybe we can define

[Bug fortran/38823] Diagnose and treat (-2.0)**2.0 properly

2009-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2009-01-13 19:55 --- Subject: Re: Diagnose and treat (-2.0)**2.0 properly On Tue, Jan 13, 2009 at 11:30:40AM -, dominiq at lps dot ens dot fr wrote: > > > --- Comment #2 from dominiq at lps dot e

[Bug fortran/38823] Diagnose and treat (-2.0)**2.0 properly

2009-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2009-01-13 19:58 --- Subject: Re: Diagnose and treat (-2.0)**2.0 properly On Tue, Jan 13, 2009 at 11:37:25AM -, dominiq at lps dot ens dot fr wrote: > > > --- Comment #3 from dominiq at lps dot e

[Bug fortran/38823] Diagnose and treat (-2.0)**2.0 properly

2009-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2009-01-13 21:30 --- Subject: Re: Diagnose and treat (-2.0)**2.0 properly On Tue, Jan 13, 2009 at 09:13:57PM -, dominiq at lps dot ens dot fr wrote: > > > --- Comment #10 from dominiq at lps dot e

[Bug fortran/40318] Complex division by zero in gfortran returns wrong results

2009-06-01 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #9 from sgk at troutmask dot apl dot washington dot edu 2009-06-01 14:56 --- Subject: Re: Complex division by zero in gfortran returns wrong results On Mon, Jun 01, 2009 at 08:35:05AM -, ghazi at gcc dot gnu dot org wrote: > > > --- Comment #2 from gha

[Bug fortran/40318] Complex division by zero in gfortran returns wrong results

2009-06-01 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2009-06-01 19:16 --- Subject: Re: Complex division by zero in gfortran returns wrong results On Mon, Jun 01, 2009 at 06:14:52PM -, ghazi at gcc dot gnu dot org wrote: > > - Comment #10 from ghazi at g

[Bug bootstrap/40439] [4.5 Regression] Bootstrap broken on FreeBSD in tree.c

2009-06-14 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2009-06-14 22:09 --- Subject: Re: [4.5 Regression] Bootstrap broken on FreeBSD in tree.c On Sun, Jun 14, 2009 at 06:02:26PM -, rguenth at gcc dot gnu dot org wrote: > > > --- Comment #1 from rguen

[Bug regression/40800] libcpp breaks bootstrap

2009-07-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2009-07-19 05:30 --- Subject: Re: libcpp breaks bootstrap On Sun, Jul 19, 2009 at 05:09:31AM -, jlquinn at optonline dot net wrote: > > > --- Comment #10 from jlquinn at optonline dot net 2009-07

[Bug regression/40800] libcpp breaks bootstrap

2009-07-20 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #18 from sgk at troutmask dot apl dot washington dot edu 2009-07-20 17:56 --- Subject: Re: libcpp breaks bootstrap On Mon, Jul 20, 2009 at 05:42:50PM -, jlquinn at optonline dot net wrote: > > > --- Comment #16 from jlquinn at optonline dot net 2009-07

[Bug regression/40800] libcpp breaks bootstrap

2009-07-20 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #20 from sgk at troutmask dot apl dot washington dot edu 2009-07-20 18:28 --- Subject: Re: libcpp breaks bootstrap On Mon, Jul 20, 2009 at 06:09:46PM -, jlquinn at gcc dot gnu dot org wrote: > > Author: jlquinn > Date: Mon Jul 20 18:09:33 2009 > New Revi

[Bug fortran/24875] [gfortran, 4.1.0 regression] Arithmetic overflow during compilation

2005-11-15 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2005-11-15 21:49 --- Subject: Re: [gfortran, 4.1.0 regression] Arithmetic overflow during compilation > Comment #5 from martin > ~/tmp>gfortran -c -fdump-parse-tree huge.f90 > >Namespace: A-Z: (UNKNOW

[Bug libfortran/25017] sqrt, csqrt may give a wrong result if real part of compex argument is zero

2005-11-24 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2005-11-24 17:22 --- Subject: Re: sqrt, csqrt may give a wrong result if real part of compex argument is zero On Thu, Nov 24, 2005 at 05:05:12PM -, pinskia at gcc dot gnu dot org wrote: > > (In reply to c

[Bug fortran/23815] Add -byteswapio flag

2005-11-27 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #21 from sgk at troutmask dot apl dot washington dot edu 2005-11-27 22:42 --- Subject: Re: Add -byteswapio flag On Sun, Nov 27, 2005 at 10:15:02PM -, tkoenig at gcc dot gnu dot org wrote: > > I have a patch (attached), but it causes quite a number of > re

[Bug libfortran/25017] sqrt, csqrt may give a wrong result if real part of compex argument is zero

2005-11-29 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2005-11-29 12:47 --- Subject: Re: sqrt, csqrt may give a wrong result if real part of compex argument is zero On Tue, Nov 29, 2005 at 09:42:05AM -, harald dot vogt at desy dot de wrote: > > > Commen

[Bug libfortran/25017] sqrt, csqrt may give a wrong result if real part of compex argument is zero

2005-11-30 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #10 from sgk at troutmask dot apl dot washington dot edu 2005-11-30 18:38 --- Subject: Re: sqrt, csqrt may give a wrong result if real part of compex argument is zero On Wed, Nov 30, 2005 at 04:17:01PM -, harald dot vogt at desy dot de wrote: > > http

[Bug libfortran/25017] sqrt, csqrt may give a wrong result if real part of compex argument is zero

2005-11-30 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2005-11-30 19:24 --- Subject: Re: sqrt, csqrt may give a wrong result if real part of compex argument is zero On Wed, Nov 30, 2005 at 10:38:13AM -0800, Steve Kargl wrote: > > Your patch is incorrect. See pa

[Bug libfortran/21820] Really, really, horrible IO performance

2005-12-09 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #18 from sgk at troutmask dot apl dot washington dot edu 2005-12-09 15:09 --- Subject: Re: Really, really, horrible IO performance On Fri, Dec 09, 2005 at 09:24:29AM -, fxcoudert at gcc dot gnu dot org wrote: > On this one, we now (due to Janne's array I/O

[Bug fortran/25578] gfortran version 4.2.0 20051227 - 144 new testsuite failures since 2005121

2005-12-27 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #1 from sgk at troutmask dot apl dot washington dot edu 2005-12-27 20:58 --- If you've only updated the source in gcc/fortran and libgfortran, then you need to do cd gcc/testsuite svn update -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25578

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-01-07 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #10 from sgk at troutmask dot apl dot washington dot edu 2006-01-07 22:17 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sat, Jan 07, 2006 at 09:55:07PM -, kargl at gcc dot gnu dot org wrote: > > > Well, in looking at the code in 25705, I

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-01-07 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #13 from sgk at troutmask dot apl dot washington dot edu 2006-01-08 01:58 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sun, Jan 08, 2006 at 12:33:29AM -, malitzke at metronets dot com wrote: > > Last things first: The code posted in 25

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-01-07 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #15 from sgk at troutmask dot apl dot washington dot edu 2006-01-08 02:43 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sun, Jan 08, 2006 at 02:30:51AM -, Tobias dot Schlueter at physik dot uni-muenchen dot de wrote: > > I find this very off

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-01-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #18 from sgk at troutmask dot apl dot washington dot edu 2006-01-08 16:37 --- Subject: Re: [meta-bug] g77 features lacking in gfortran On Sun, Jan 08, 2006 at 10:41:15AM -, malitzke at metronets dot com wrote: > > one had called your work a piece of exc

[Bug fortran/25486] [4.1/4.2 Regression] fortran fixed-form literal character constant not padded.

2006-01-10 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2006-01-11 01:45 --- Subject: Re: [4.1/4.2 Regression] fortran fixed-form literal character constant not padded. On Tue, Jan 10, 2006 at 10:00:34PM -, steven at gcc dot gnu dot org wrote: > > The patch doe

[Bug fortran/25756] ICE on valid code with labels

2006-01-12 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2006-01-12 22:41 --- Subject: Re: ICE on valid code with labels On Thu, Jan 12, 2006 at 08:18:50PM -, kargl at gcc dot gnu dot org wrote: > > get rids of the ICE, but I don't understand why we hav

[Bug fortran/25756] ICE on valid code with labels

2006-01-13 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2006-01-13 22:20 --- Subject: Re: ICE on valid code with labels On Fri, Jan 13, 2006 at 10:15:13PM -, aldot at gcc dot gnu dot org wrote: > > Should the warning be made consistent between fixed- and fre

[Bug fortran/28548] [4.2 Regression]: Optional argument failed

2006-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2006-08-03 05:09 --- Subject: Re: [4.2 Regression]: Optional argument failed On Thu, Aug 03, 2006 at 04:49:33AM -, kargl at gcc dot gnu dot org wrote: > > (gdb) print *isym > $28 = {name =

[Bug fortran/28548] [4.2 Regression]: Optional argument failed

2006-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2006-08-03 06:26 --- Subject: Re: [4.2 Regression]: Optional argument failed On Thu, Aug 03, 2006 at 06:22:10AM -, martin at mpa-garching dot mpg dot de wrote: > > My understanding of this is that the

[Bug fortran/28548] [4.2 Regression]: Optional argument failed

2006-08-03 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #10 from sgk at troutmask dot apl dot washington dot edu 2006-08-03 16:17 --- Subject: Re: [4.2 Regression]: Optional argument failed On Thu, Aug 03, 2006 at 06:40:21AM -, martin at mpa-garching dot mpg dot de wrote: > Hmm, but my point was that even if gfort

[Bug fortran/28276] EXPONENT() broken for real constants

2006-09-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2006-09-11 19:19 --- Subject: Re: EXPONENT() broken for real constants On Sun, Sep 10, 2006 at 10:43:21PM -, tobias dot burnus at physik dot fu-berlin dot de wrote: > > Comment #5 from tobias dot bur

[Bug fortran/28276] EXPONENT() broken for real constants

2006-09-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-09-11 19:33 --- Subject: Re: EXPONENT() broken for real constants On Mon, Sep 11, 2006 at 07:19:41PM -, sgk at troutmask dot apl dot washington dot edu wrote: > > gfortran is calling the wrong libm fu

[Bug fortran/28276] EXPONENT() broken for real constants

2006-09-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2006-09-11 20:31 --- Subject: Re: EXPONENT() broken for real constants On Mon, Sep 11, 2006 at 07:33:35PM -, sgk at troutmask dot apl dot washington dot edu wrote: > > I should also note that the pars

[Bug fortran/29317] gfortran.dg/exponent_1.f90 failure

2006-10-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #1 from sgk at troutmask dot apl dot washington dot edu 2006-10-02 14:22 --- Subject: Re: New: gfortran.dg/exponent_1.f90 failure On Mon, Oct 02, 2006 at 09:32:55AM -, fxcoudert at gcc dot gnu dot org wrote: > gfortran.dg/exponent_1.f90 is failing at all optimizat

[Bug fortran/29317] gfortran.dg/exponent_1.f90 failure

2006-10-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2006-10-02 15:00 --- Subject: Re: gfortran.dg/exponent_1.f90 failure On Mon, Oct 02, 2006 at 02:27:47PM -, Francois-Xavier dot Coudert at ens dot fr wrote: > > > --- Comment #2 from Francois-X

[Bug fortran/29317] gfortran.dg/exponent_1.f90 failure

2006-10-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2006-10-02 19:08 --- Subject: Re: New: gfortran.dg/exponent_1.f90 failure On Mon, Oct 02, 2006 at 09:32:55AM -, fxcoudert at gcc dot gnu dot org wrote: > gfortran.dg/exponent_1.f90 is failing at all optimizat

[Bug fortran/18026] boz initialization of REALs fails

2006-10-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #10 from sgk at troutmask dot apl dot washington dot edu 2006-10-03 01:48 --- Subject: Re: boz initialization of REALs fails On Mon, Oct 02, 2006 at 09:35:11PM -, anlauf at gmx dot de wrote: > > > This is NOT a bug. g77 compatibility and the Fortran 95

[Bug fortran/29317] gfortran.dg/exponent_1.f90 failure

2006-10-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-10-03 02:27 --- Subject: Re: gfortran.dg/exponent_1.f90 failure On Tue, Oct 03, 2006 at 02:12:55AM -, danglin at gcc dot gnu dot org wrote: > > The gfortran.dg/exponent_1.f90 and gfortran.dg/nearest

[Bug libfortran/29423] FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90

2006-10-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2006-10-11 16:53 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90 On Wed, Oct 11, 2006 at 04:30:20PM -, dave at hiauly1 dot hia dot nrc dot ca wrote

[Bug libfortran/29423] FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90

2006-10-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2006-10-11 18:30 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90 > > Does youir OS have fabsf, frexpf, and ldexpf? > > Yes, no, no. It has fre

[Bug libfortran/29423] FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90

2006-10-11 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-10-12 04:51 --- Subject: Re: FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 and intrinsic_spacing.f90 On Wed, Oct 11, 2006 at 09:45:02PM -, dave at hiauly1 dot hia dot nrc dot ca wrote

[Bug fortran/29067] Internal Error: gfc_resolve_expr(): Bad expression type

2006-10-12 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-10-12 14:13 --- Subject: Re: Internal Error: gfc_resolve_expr(): Bad expression type On Thu, Oct 12, 2006 at 12:18:30PM -, pault at gcc dot gnu dot org wrote: > > > --- Comment #6 from pault a

[Bug fortran/30605] -Wno-tabs should be active for -std=f2003 and -pedantic

2007-01-30 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-01-30 23:09 --- Subject: Re: -Wno-tabs should be active for -std=f2003 and -pedantic On Tue, Jan 30, 2007 at 11:06:24PM -, jb at gcc dot gnu dot org wrote: > > --- Comment #4 from jb at gcc dot g

[Bug fortran/30683] [4.2 only] internal compiler error: Segmentation fault

2007-02-03 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2007-02-03 17:45 --- Subject: Re: [4.2 only] internal compiler error: Segmentation fault On Sat, Feb 03, 2007 at 12:05:53PM -, sfilippone at uniroma2 dot it wrote: > > > I'm testing a patch f

[Bug fortran/30834] ICE with kind=8 exponentiaton

2007-02-17 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2007-02-17 21:51 --- Subject: Re: ICE with kind=8 exponentiaton On Sat, Feb 17, 2007 at 09:27:07PM -, tkoenig at gcc dot gnu dot org wrote: > > > After looking at this a little bit, I think we ma

[Bug fortran/30834] ICE with kind=8 exponentiaton

2007-02-19 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2007-02-19 21:49 --- Subject: Re: ICE with kind=8 exponentiaton On Mon, Feb 19, 2007 at 09:11:45PM -, tkoenig at gcc dot gnu dot org wrote: > > >Feel free to create a gfc_extract_long_long and docu

[Bug fortran/30883] procedure with dummy procedure f1 rejected with implicit none

2007-02-20 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2007-02-20 22:56 --- Subject: Re: procedure with dummy procedure f1 rejected with implicit none On Tue, Feb 20, 2007 at 10:41:11PM -, kargl at gcc dot gnu dot org wrote: > > I haven't located the re

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2007-02-23 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2007-02-23 21:02 --- Subject: Re: various intrinsics do not diagnose invalid argument kinds On Fri, Feb 23, 2007 at 08:42:03PM -, burnus at gcc dot gnu dot org wrote: > > > > various intrinsics do

[Bug libfortran/31052] Bad IOSTAT values when readings NAMELISTs past EOF

2007-03-06 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2007-03-06 15:53 --- Subject: Re: Bad IOSTAT values when readings NAMELISTs past EOF On Tue, Mar 06, 2007 at 08:20:23AM -, anlauf at gmx dot de wrote: > > > --- Comment #3 from anlauf at gmx dot de

[Bug fortran/29471] Warn with -std=f95/f2003 when BOZ is used at invalid places

2007-03-15 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2007-03-16 04:07 --- Subject: Re: Warn with -std=f95/f2003 when BOZ is used at invalid places On Fri, Mar 16, 2007 at 03:46:30AM -, jkrahn at nc dot rr dot com wrote: > > > --- Comment #5 from jkr

[Bug fortran/29471] Warn with -std=f95/f2003 when BOZ is used at invalid places

2007-03-15 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2007-03-16 04:09 --- Subject: Re: Warn with -std=f95/f2003 when BOZ is used at invalid places On Fri, Mar 16, 2007 at 03:53:57AM -, jkrahn at nc dot rr dot com wrote: > > I have not checked F2008 yet. My v

[Bug libfortran/31052] Bad IOSTAT values when readings NAMELISTs past EOF

2007-03-19 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #21 from sgk at troutmask dot apl dot washington dot edu 2007-03-20 01:47 --- Subject: Re: Bad IOSTAT values when readings NAMELISTs past EOF On Mon, Mar 19, 2007 at 10:59:25PM -, anlauf at gmx dot de wrote: > > > --- Comment #20 from anlauf at gmx dot

[Bug fortran/32942] Wrong code with with -fdefault-integer-8

2007-07-31 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #2 from sgk at troutmask dot apl dot washington dot edu 2007-07-31 18:40 --- Subject: Re: Wrong code with with -fdefault-integer-8 On Tue, Jul 31, 2007 at 06:04:02PM -, kargl at gcc dot gnu dot org wrote: > > > I have reduced the failure for intrinsic_rrsp

[Bug fortran/32942] Wrong code with with -fdefault-integer-8

2007-07-31 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2007-07-31 19:37 --- Subject: Re: Wrong code with with -fdefault-integer-8 On Tue, Jul 31, 2007 at 06:56:33PM -, dominiq at lps dot ens dot fr wrote: > > > So, we need to review every unilater

[Bug fortran/32942] Wrong code with with -fdefault-integer-8

2007-07-31 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #9 from sgk at troutmask dot apl dot washington dot edu 2007-07-31 20:50 --- Subject: Re: Wrong code with with -fdefault-integer-8 On Tue, Jul 31, 2007 at 08:32:56PM -, dominiq at lps dot ens dot fr wrote: > > > --- Comment #7 from dominiq at lps dot e

[Bug fortran/32942] Wrong code with with -fdefault-integer-8

2007-07-31 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #12 from sgk at troutmask dot apl dot washington dot edu 2007-07-31 21:48 --- Subject: Re: Wrong code with with -fdefault-integer-8 On Tue, Jul 31, 2007 at 09:39:28PM -, dominiq at lps dot ens dot fr wrote: > > > The rrspacing problem is something besides

[Bug fortran/32942] Wrong code with with -fdefault-integer-8

2007-07-31 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #14 from sgk at troutmask dot apl dot washington dot edu 2007-07-31 22:29 --- Subject: Re: Wrong code with with -fdefault-integer-8 On Tue, Jul 31, 2007 at 10:04:55PM -, dominiq at lps dot ens dot fr wrote: > > > It is an opteron, so little endian. > &g

[Bug testsuite/32956] Compiling equiv_7_db.f90 gives an error with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-08-02 20:32 --- Subject: Re: Compiling equiv_7_db.f90 gives an error with -fdefault-integer-8 On Thu, Aug 02, 2007 at 08:26:44PM -, tkoenig at gcc dot gnu dot org wrote: > > If we use -fdefault-intege

[Bug fortran/32968] selected_(int|real)_kind fail with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2007-08-02 21:06 --- Subject: Re: selected_(int|real)_kind fail with -fdefault-integer-8 On Thu, Aug 02, 2007 at 10:55:45PM +0200, Dominique Dhumieres wrote: > > I applied your patch, but on PPC Darwin I

[Bug fortran/32968] selected_(int|real)_kind fail with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-08-02 21:42 --- Subject: Re: selected_(int|real)_kind fail with -fdefault-integer-8 On Thu, Aug 02, 2007 at 11:17:02PM +0200, Dominique Dhumieres wrote: > > look to yours, but with -fdefault-integer-8,

[Bug fortran/32968] selected_(int|real)_kind fail with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #6 from sgk at troutmask dot apl dot washington dot edu 2007-08-02 22:29 --- Subject: Re: selected_(int|real)_kind fail with -fdefault-integer-8 On Thu, Aug 02, 2007 at 11:17:02PM +0200, Dominique Dhumieres wrote: > > look to yours, but with -fdefault-integer-8,

[Bug fortran/32968] selected_(int|real)_kind fail with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #9 from sgk at troutmask dot apl dot washington dot edu 2007-08-02 23:49 --- Subject: Re: selected_(int|real)_kind fail with -fdefault-integer-8 On Thu, Aug 02, 2007 at 11:02:55PM -, dominiq at lps dot ens dot fr wrote: > > > --- Comment #8 from domin

[Bug fortran/32968] selected_(int|real)_kind fail with -fdefault-integer-8

2007-08-02 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #10 from sgk at troutmask dot apl dot washington dot edu 2007-08-03 00:04 --- Subject: Re: selected_(int|real)_kind fail with -fdefault-integer-8 On Thu, Aug 02, 2007 at 11:02:55PM -, dominiq at lps dot ens dot fr wrote: > > I think you need the same k

[Bug fortran/32979] Implement vendor-specific ISNAN() intrinsic function

2007-08-03 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2007-08-03 20:33 --- Subject: Re: Implement vendor-specific ISNAN() intrinsic function On Fri, Aug 03, 2007 at 08:25:08PM -, burnus at gcc dot gnu dot org wrote: > > > If we're going to implement

[Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f*

2007-08-04 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-08-04 17:00 --- Subject: Re: TAB in FORMAT: accept extension, warn with -std=f* On Sat, Aug 04, 2007 at 04:53:33PM -, burnus at gcc dot gnu dot org wrote: > > > I therefore suggest: > - Silentl

[Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f*

2007-08-09 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #11 from sgk at troutmask dot apl dot washington dot edu 2007-08-10 03:50 --- Subject: Re: TAB in FORMAT: accept extension, warn with -std=f* On Fri, Aug 10, 2007 at 03:27:33AM -, satyaakam at yahoo dot co dot in wrote: > > Any plans to backport. > No.

[Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f*

2007-08-30 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #13 from sgk at troutmask dot apl dot washington dot edu 2007-08-30 22:24 --- Subject: Re: TAB in FORMAT: accept extension, warn with -std=f* On Thu, Aug 30, 2007 at 09:52:56PM -, fago at caltech dot edu wrote: > > --- Comment #12 from fago at caltech d

[Bug fortran/33339] GFORTRAN OPTIMIZATION ERROR ABOVE -O0 FOR MPICH2 TEST F90_RMA/BASEATTRWINF90.F90

2007-09-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2007-09-08 19:17 --- Subject: Re: GFORTRAN OPTIMIZATION ERROR ABOVE -O0 FOR MPICH2 TEST F90_RMA/BASEATTRWINF90.F90 > > >>> ftn -o x -O2 bug2867.f90 > >>> aprun -n 1 ./x > >>&g

[Bug fortran/33339] GFORTRAN OPTIMIZATION ERROR ABOVE -O0 FOR MPICH2 TEST F90_RMA/BASEATTRWINF90.F90

2007-09-10 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-09-10 18:28 --- Subject: Re: GFORTRAN OPTIMIZATION ERROR ABOVE -O0 FOR MPICH2 TEST F90_RMA/BASEATTRWINF90.F90 On Mon, Sep 10, 2007 at 04:03:21PM -, longb at cray dot com wrote: > > gcc version

[Bug fortran/31244] data initialization with more than 2**32 elements

2007-09-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #2 from sgk at troutmask dot apl dot washington dot edu 2007-09-18 18:02 --- Subject: Re: data initialization with more than 2**32 elements On Tue, Sep 18, 2007 at 05:56:36PM -, kargl at gcc dot gnu dot org wrote: > > The problem is found in decl.c(top_val_li

[Bug fortran/31244] data initialization with more than 2**32 elements

2007-09-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #3 from sgk at troutmask dot apl dot washington dot edu 2007-09-18 19:16 --- Subject: Re: data initialization with more than 2**32 elements On Tue, Sep 18, 2007 at 06:02:03PM -, sgk at troutmask dot apl dot washington dot edu wrote: > > > > The problem

[Bug fortran/31244] data initialization with more than 2**32 elements

2007-09-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2007-09-18 19:26 --- Subject: Re: data initialization with more than 2**32 elements On Tue, Sep 18, 2007 at 07:16:42PM -, sgk at troutmask dot apl dot washington dot edu wrote: > > Ugh. I have a patc

[Bug fortran/31244] data initialization with more than 2**32 elements

2007-09-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-09-18 20:07 --- Subject: Re: data initialization with more than 2**32 elements On Tue, Sep 18, 2007 at 07:26:22PM -, sgk at troutmask dot apl dot washington dot edu wrote: > > If I'm not mistaken

[Bug fortran/33544] Spurious warning in TRANSFER intrinsic in Sept 24 snapshot of gfortran

2007-09-24 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-09-24 19:59 --- Subject: Re: Spurious warning in TRANSFER intrinsic in Sept 24 snapshot of gfortran On Mon, Sep 24, 2007 at 07:17:54PM -, burnus at gcc dot gnu dot org wrote: > > > --- Commen

[Bug fortran/33544] Spurious warning in TRANSFER intrinsic in Sept 24 snapshot of gfortran

2007-09-24 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2007-09-24 21:49 --- Subject: Re: Spurious warning in TRANSFER intrinsic in Sept 24 snapshot of gfortran On Mon, Sep 24, 2007 at 09:26:01PM -, pinskia at gmail dot com wrote: > On 24 Sep 2007 19:59:37 -0000,

[Bug middle-end/20030] [4.0 Regression] Broken arguments access

2005-02-17 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-17 19:17 --- Tobi, thanks for adding me to the CC list. Andrew's patch fixes the problems with BLAS. I extemely happy someone else was able to find a small testcase, because I was starting to tri

[Bug fortran/20063] gfortran assembler error - : Bad Absolute Expression, absolute 0 assumed.

2005-02-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-18 21:01 --- Your code compiles fine on amd64-*-freebsd where I'm using a gfortran form 20050218 sources. I do get a warning though troutmask:kargl[205] /usr/tmp/sgk/bin/gfc -c e.f /var/tmp/ccvV0

[Bug fortran/20058] Error on kind 16 hex data statement

2005-02-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-18 22:48 --- I have a tentative patch for this problem. Unfortunately, it leads to a different problem. It appears that if your system supports integer(kind=16), then gfortran can't print the v

[Bug libfortran/20085] iargc returns wrong count for number of program arguments

2005-02-19 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-02-20 05:00 --- Patch is here http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01148.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20085

[Bug fortran/20248] gfortran: intrinsics and std=f95, inconsistency with other compilers

2005-02-28 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-03-01 01:02 --- Read the F2003 standard. 5.1.2.8INTRINSIC attribute The INTRINSIC attribute confirms that a name is the specific name (13.6) or generic name (13.5) of an intrinsic procedure. When you

[Bug fortran/20335] ICE with attached Fortran source

2005-03-06 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-03-06 17:00 --- Subject: Re: ICE with attached Fortran source On Sun, Mar 06, 2005 at 04:37:26PM -, tobi at gcc dot gnu dot org wrote: > > --- Additional Comments From tobi at gcc dot g

[Bug other/20390] New: Options aren't handled by LANG_HOOKS_HANDLE_OPTIONS

2005-03-08 Thread sgk at troutmask dot apl dot washington dot edu
Summary: Options aren't handled by LANG_HOOKS_HANDLE_OPTIONS Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: other AssignedTo: unassigned at gcc dot gnu dot org Report

[Bug other/20390] Options aren't handled by LANG_HOOKS_HANDLE_OPTIONS

2005-03-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-03-08 23:47 --- Subject: Re: Options aren't handled by LANG_HOOKS_HANDLE_OPTIONS On Tue, Mar 08, 2005 at 11:21:52PM -, pinskia at gcc dot gnu dot org wrote: > > --- Additional Co

[Bug driver/13464] -i8 and -r8 not passed correctly to compiler proper. and -d8 does not work

2005-03-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-03-08 23:52 --- The gfortran frontend defines the two options -i8 and -r8 in gfortran/lang.opt. gcc/opts.sh appears to process lang.opt without a problem, because the produced options.h file contains

[Bug other/20390] Options aren't handled by LANG_HOOKS_HANDLE_OPTIONS

2005-03-08 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-03-08 23:53 --- *** This bug has been marked as a duplicate of 13464 *** -- What|Removed |Added

  1   2   3   >