[Bug fortran/40037] gfortran -O3 optimization generates code that seg faults on unaligned array data

2009-05-06 Thread mick at nag dot co dot uk
--- Comment #2 from mick at nag dot co dot uk 2009-05-06 08:45 --- (In reply to comment #1) > I think this is not a valid Fortran program. > The main program is illegal because it passes a REAL array argument to a subroutine expecting DOUBLE PRECISION array. However, the subr

[Bug fortran/40037] New: gfortran -O3 optimization generates code that seg faults on unaligned array data

2009-05-06 Thread mick at nag dot co dot uk
ata Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mick at nag dot co dot uk GCC build triplet: x86_64-un

[Bug fortran/24406] EQUIVALENCE broken in 32-bit code with optimization -O2

2006-04-24 Thread mick at nag dot co dot uk
--- Comment #18 from mick at nag dot co dot uk 2006-04-24 10:13 --- Subject: Re: EQUIVALENCE broken in 32-bit code with optimization -O2 pault at gcc dot gnu dot org wrote: > --- Comment #17 from pault at gcc dot gnu dot org 2006-04-23 06:07 > --- > This has b

[Bug fortran/24406] New: EQUIVALENCE broken in 32-bit code with optimization -O2

2005-10-17 Thread mick at nag dot co dot uk
00 -- Summary: EQUIVALENCE broken in 32-bit code with optimization -O2 Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu

[Bug libfortran/24313] New: complex sqrt function does not return principal value

2005-10-11 Thread mick at nag dot co dot uk
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mick at nag dot co dot uk GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24313

[Bug fortran/24261] gfortran ALLOCATE statement does not align objects on 16-byte boundary

2005-10-11 Thread mick at nag dot co dot uk
--- Comment #3 from mick at nag dot co dot uk 2005-10-11 09:26 --- Thanks - the problem is now fixed in 64-bit compilations. However, if I compile try.f and sub.c with the -m32 flag, I still get memory allocated on 8-byte boundaries rather than 16-byte. As Andrew said, this is down to

[Bug fortran/24261] New: gfortran ALLOCATE statement does not align objects on 16-byte boundary

2005-10-07 Thread mick at nag dot co dot uk
Summary: gfortran ALLOCATE statement does not align objects on 16-byte boundary Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at g

[Bug fortran/22345] Internal compiler error compiling BLAS routine dspr.f

2005-07-08 Thread mick at nag dot co dot uk
--- Additional Comments From mick at nag dot co dot uk 2005-07-08 13:32 --- Subject: Re: Internal compiler error compiling BLAS routine dspr.f pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-07 > 13:20 -

[Bug fortran/22345] New: Internal compiler error compiling BLAS routine dspr.f

2005-07-07 Thread mick at nag dot co dot uk
ine dspr.f Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mick at nag dot co dot uk CC: gcc-bugs

[Bug fortran/22342] New: Internal write to character array causes "internal compiler error"

2005-07-07 Thread mick at nag dot co dot uk
0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mick at nag dot co dot uk CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22342

[Bug fortran/21381] New: Internal compiler error: in set_value_range

2005-05-04 Thread mick at nag dot co dot uk
org ReportedBy: mick at nag dot co dot uk CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21381