ot gnu dot org
ReportedBy: refson dot temp at ntlworld dot com
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34788
--- Comment #1 from refson dot temp at ntlworld dot com 2007-06-24 10:09
---
Created an attachment (id=13773)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13773&action=view)
Test case source
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32478
: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: refson dot temp at ntlworld dot com
GCC host triplet: i386-pc-linux-gnu
GCC target triplet: i386-pc-linux
org
ReportedBy: refson dot temp at ntlworld dot com
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29563
--- Comment #3 from refson dot temp at ntlworld dot com 2006-10-23 13:48
---
For the record
[EMAIL PROTECTED] New_Code_TCM]$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /home/fxcoudert/gfortran_nightbuild/trunk/configure
--prefix=/home/fxcoudert
--- Comment #2 from refson dot temp at ntlworld dot com 2006-10-23 13:46
---
Sorry. This is on a 32-bit AMD Athlon 1800+ processor. I assume the issue
doesn't
arise on 64-bit hardware.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29562
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: refson dot temp at ntlworld dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29562
--- Additional Comments From refson dot temp at ntlworld dot com
2005-07-24 10:36 ---
Please accept my apologies. I had not realised that this was a
gcc-developers-only site and that bug reports from users are not
welcome. I have no expertise in compiler development so the
likelyhood
--- Additional Comments From refson dot temp at ntlworld dot com
2005-03-23 11:16 ---
This bug is a complete showstopper, but has been sitting unresolved
for 6 months. Is there any way to increase the priority and actually
have it assigned to anyone? There is no way to even test that
