--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-11-29 03:50
---
Dang, I just noticed that Iwan had proposed a patch in comment #5 so I did my
own.
My apologies please.
Does Iwan have copyright assignment in place?
I took a different approach with my patch because I did not
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-29 02:28
---
Yes, I have a patch under review right now that fixes this. However, I am
going to add a requirement that -std=legacy or similar be invoked, otherwise we
would be non-compliant with F95 Standard which disallows c
--- Comment #8 from kargl at gcc dot gnu dot org 2005-11-29 01:55 ---
(In reply to comment #7)
> (In reply to comment #6)
> I'm not sure what the "correct" behavior is.
> But it is a fact that gfortran is the first
> compiler I have seen to respond with a runtime error,
> given this f
--- Comment #7 from iwan at irs dot phy dot nrc dot ca 2005-11-29 00:35
---
(In reply to comment #6)
I'm not sure what the "correct" behavior is.
But it is a fact that gfortran is the first
compiler I have seen to respond with a runtime error,
given this format and input. This is ext
--- Comment #6 from kargl at gcc dot gnu dot org 2005-11-29 00:08 ---
The error is actually correct behavior. The comma is
not a valid character in an integer and the '(2I9)'
format is telling the compiler that you are inputting
2 integers with 9 digits each. The comma does not
short-c
--- Comment #5 from iwan at irs dot phy dot nrc dot ca 2005-11-28 20:22
---
Created an attachment (id=10358)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10358&action=view)
Fixes bug 25039
The patch is against revision 107612 on gcc trunc,
to be applied in gcc/libgfortran/io.
I
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-26 19:10
---
The problem with the test case is not related to the weird dump I am getting.
Notice I also have a 'Y' in there too as well as a '\b' character. This is
really weird.
I also noticed some namelist failures in th
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2005-11-26 09:58
---
(In reply to comment #2)
> What is this unprintable character? Is that right?
I don't see an unprintable character in my i686-linux dump:
MAIN__ ()
{
int4 i1;
int4 i2;
{
struct __st_parameter_dtquire
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-26 01:35
---
-fdump-tree-original: See below. What is this unprintable character? Is that
right?
MAIN__ ()
{
int4 i2;
int4 i1;
{
struct __st_parameter_dtquireY dt_parm.0;
dt_parm.0.common.filename = "junk.
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-25 22:00
---
Confirmed on 4.2
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
Assig
10 matches
Mail list logo
