--- Comment #18 from jvdelisle at gcc dot gnu dot org 2007-07-27 16:53
---
Fixed on 4.3
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2007-07-27 20:40
---
Dominique,
I have the same problem as FX. I do not have access to this platform. If I
could secure shell (ssh) into one of these, I would work on this.
Your idea on the order of #defines is probably on the
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2007-07-28 15:29
---
Created an attachment (id=13994)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13994&action=view)
Example of bad translation
This attached example of tree-dump-original shows that we are ge
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-07-28 15:37
---
I will mention that pr31213 has multiple problems. We have a partial fix that
appears to take care of one of these. So if you get a reduced case here, we
can try it.
--
http://gcc.gnu.org/bugzilla
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-07-28 15:56
---
I will take care of this one
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-07-28 15:57
---
This is most likely mine.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-07-28 16:13
---
I believe that valgrind is showing this because the st_parameter_common
structure "cmp" is set at compile time. The options.locus parameter is
initialized to zero in environ.c
--
jvdelisle at gcc d
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2007-07-28 21:17
---
Subject: Bug 31609
Author: jvdelisle
Date: Sat Jul 28 21:17:20 2007
New Revision: 127026
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127026
Log:
2007-07-28 Jerry DeLisle <[EMAI
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2007-07-28 22:02
---
Subject: Bug 31609
Author: jvdelisle
Date: Sat Jul 28 22:02:42 2007
New Revision: 127028
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127028
Log:
2007-07-29 Jerry DeLisle <[EMAI
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-07-28 22:33
---
I think this is ignorable. We allocate a buffer of 8192 bytes. We only use a
portion of it, so the pointer to that block is being flagged as pointing to
uninitialized memory. We don't want to tak
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-07-29 23:23
---
The patch applied in Comment #11 fixes the original test case.
The modified test case in Comment #8 is still broken.
pr31609-2.f90: In function master.0.j:
pr31609-2.f90:10: internal compiler error: in
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2007-07-31 01:39
---
Regression tests fine on X86-64-Gnu/Linux
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31609
Priority: P3
Component: libfortran
AssignedTo: jvdelisle at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33019
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-08 02:18
---
Created an attachment (id=14040)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14040&action=view)
Namelist input file
Test case using attached input:
PROGRAM namelist
CHARACTER*
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-08 02:19
---
Created an attachment (id=14041)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14041&action=view)
Namelist input file
Correct input file.
--
jvdelisle at gcc dot gnu dot org changed:
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-09 23:27
---
Regarding the test case:
&codechar='Improper lower case name',X=-3.0/
Fortran 95 Standard 10.9.1 states:
"If a processor is capable of representing letters in both upper and lower
ca
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-09 23:37
---
*** Bug 33019 has been marked as a duplicate of this bug. ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-09 23:37
---
*** This bug has been marked as a duplicate of 33039 ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-08-09 23:38
---
This report is better than my own. :)
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-08-10 03:00
---
write_float uses isfinite (n) and isnan (n) to determine if "Infinite" or "NaN"
is emitted and in that case exits before calling output_float. So if execution
is reaching output_float
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-08-10 12:43
---
Fixed on 4.3
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-08-10 12:36
---
Subject: Bug 33039
Author: jvdelisle
Date: Fri Aug 10 12:36:01 2007
New Revision: 127332
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127332
Log:
2007-08-10 Jerry DeLisle <[EMAI
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-08-10 12:40
---
Subject: Bug 33039
Author: jvdelisle
Date: Fri Aug 10 12:39:46 2007
New Revision: 127333
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127333
Log:
2007-08-10 Jerry DeLisle <[EMAI
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-08-11 15:04
---
Regarding comment #7, The finite and nan have no meaning in the context of
binary, octal, or hex output.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26252
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2007-08-11 15:38
---
Changing to enhancement. STANDARD I/O works fine.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #24 from jvdelisle at gcc dot gnu dot org 2007-08-11 17:49
---
Sorry for the spin up here. I have a patch ready, still trying to test.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-12 19:47
---
I will give this a shot.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-14 05:25
---
This makes some sense: The following reduced case works fine with
-fdefault-integer-8 with iostat given and gives an error without it. I could
argue that this is OK. I have not dug into the standard on this
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-18 17:42
---
When using list directed formatting, the default for a string appends a " "
(space) in front of the output. If you replace * with '(a)' you will see that
it is fine. Why the others accept it
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2007-08-18 19:39
---
I will try to have a look in the next few days.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30162
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2007-08-19 19:45
---
This works on 4.2 and 4.3. Not planning to backport to 4.1. See if you can
get a later version of gfortran. If you have problems doing so, check the
gfortran wiki binaries. If that fails, let me know
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
GCC host triplet: ppc64 Power5
http://gcc.gnu.org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-23 05:49
---
I was able to successfully build gcc 3.4.6 and attempted to use that to build
gcc 4.3.0. I get the same failure in stage 2. I have also updated the
binutils to no avail.
--
http://gcc.gnu.org/bugzilla
3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
GCC host triplet: i686-pc-Cygwin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33177
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-25 02:12
---
This only occurs with kind=10. Unformatted io writes sets only 12 of the 16
bytes that are wriiten for a KIND=10 value.
Closing
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-25 14:02
---
I will have a look
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-25 16:20
---
>From 9.4.1
R913format is default-char-expr
or label
or ∗
>From 10.1.2
A character expression used as a format specifier in a formatted
input/output statement shall evalu
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-25 16:26
---
All that garbage string ∗ is an * (asterisk)
Character encoding got cobbled up there.
I want to add that the key to this question is that '*' is a character
expression form of the format specifier
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-08-25 18:03
---
The * is not an "edit-descriptor" see 10.2
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33189
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-25 18:23
---
I see the fix upstream. FX, do you have an idea of the time it will take for
this to make it into Cygwin update?
I don't want to post a new Cygwin gfortran binary until this is fixed.
--
http://gcc.gn
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-26 01:55
---
I am going to try this one.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-08-26 22:05
---
Subject: Bug 33055
Author: jvdelisle
Date: Sun Aug 26 22:04:48 2007
New Revision: 127817
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127817
Log:
2007-08-26 Jerry DeLisle <[EMAI
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-08-26 22:19
---
Subject: Bug 33055
Author: jvdelisle
Date: Sun Aug 26 22:19:18 2007
New Revision: 127819
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127819
Log:
2007-08-26 Jerry DeLisle <[EMAI
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-08-26 22:24
---
Fixed on trunk.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-29 01:27
---
I think the problem has to do with not having a backend_decl associated with
the dummy variable expression created. I will not be able to get to this
quickly, so I will revert the patch until I get this fixed
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-08-29 02:26
---
Subject: Bug 33055
Author: jvdelisle
Date: Wed Aug 29 02:26:01 2007
New Revision: 127877
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127877
Log:
2007-08-28 Jerry DeLisle <[EMAI
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-30 00:52
---
The patch has not been reversed yet. This is a duplicate of PR33225. Since
there is more information in the other PR, I will close this one and track on
the other.
I can reproduce the bug using -m32 on my
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-30 00:53
---
*** This bug has been marked as a duplicate of 33225 ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-08-30 00:53
---
*** Bug 33223 has been marked as a duplicate of this bug. ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-08-30 00:55
---
Test case from PR33223.
program t
print*,huge(1.0d0),tiny(1.0d0)
end program t
gives the output
1.797693134862316E+30^@ 2.225073858507201E-30^@
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33225
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-30 04:59
---
Reverted patch from PR33055
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-08-30 05:01
---
The following ICEs the the above patches which I reverted until I sort this
out.
MODULE print_it
CONTAINS
SUBROUTINE i()
LOGICAL :: qexist
INQUIRE (UNIT=1, EXIST=qexist)
END SUBROUTINE i
END MODULE
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2007-08-31 01:43
---
Patch causing regression reverted. Closing this PR. Thanks for reporting.
The next round on the per kind write float patch will have these test cases
addressed.
--
jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-08-31 01:44
---
'*' is not valid so closing.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2007-08-31 01:37
---
Subject: Bug 33225
Author: jvdelisle
Date: Fri Aug 31 01:37:31 2007
New Revision: 127950
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127950
Log:
2007-08-30 Jerry DeLisle <[EMAI
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-08-31 02:39
---
As Andrew stated, most of these testsuite failures were due to a regression
caused by one of my patches. I do monitor bugzilla submissions during the day.
However, I do this work in the evenings as a volunteer
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-31 19:47
---
gfortran does catch these at run time.
Also, the last case, read ('f3.3'), a, does give a legitimate error:
read ('f3.3'), a
1
Error: UNIT specification at (1) must be an INTEGER expre
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-31 20:17
---
I want to study this a bit. I think it is a bug.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-08-31 20:05
---
The print case is rejected at run time. See PR28397. IMHO
print('a'), 'Hello' ! Invalid, caught at run time, no leading paren
! in char expr.
write(*,('(a)&
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-08-31 20:48
---
Point well taken. Tobias, I will work this one unless you wish to do so.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33268
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-09-02 16:08
---
Well, it has not been on my top burner. Looking at -fdump-tree-original the
problem can be seen easily. Fixing is not so straight forward. This will
probably not happen until 4.4.
--
http://gcc.gnu.org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-09-02 20:57
---
This is assuming that an asymmetric range is permitted in Fortran which I think
it is not. You can use -fno-range-check to disable this check.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33285
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-09-03 19:27
---
Subject: Bug 33253
Author: jvdelisle
Date: Mon Sep 3 19:27:48 2007
New Revision: 128056
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128056
Log:
2007-09-03 Jerry DeLisle <[EMAI
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-09-03 19:29
---
Subject: Bug 33253
Author: jvdelisle
Date: Mon Sep 3 19:29:17 2007
New Revision: 128057
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128057
Log:
2007-09-03 Jerry DeLisle <[EMAI
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-09-03 19:32
---
Fixed on trunk.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2007-09-04 04:47
---
Found the problem. I will submit the update patch against this PR
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-09-04 04:49
---
Changed title to reflect what this is, not really a regression at this point.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2007-09-04 05:39
---
Yes, I also checked the huge testcase and its all clean now.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33225
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2007-09-04 05:44
---
Dominique: The problem in comment 14 is not fixed and I do not think its
related. I will check further though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33225
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-09-05 00:11
---
I have been waiting for this to emerge. We knew there was a problem somewhere.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2007-09-05 00:51
---
Subject: Bug 33225
Author: jvdelisle
Date: Wed Sep 5 00:51:18 2007
New Revision: 128114
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128114
Log:
2007-03-04 Jerry DeLisle <[EMAI
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2007-09-06 01:20
---
Subject: Bug 33253
Author: jvdelisle
Date: Thu Sep 6 01:20:02 2007
New Revision: 128170
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128170
Log:
2007-09-05 Jerry DeLisle <[EMAI
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-09-06 01:24
---
Subject: Bug 33253
Author: jvdelisle
Date: Thu Sep 6 01:24:17 2007
New Revision: 128171
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128171
Log:
2007-09-06 Jerry DeLisle <[EMAI
--- Comment #22 from jvdelisle at gcc dot gnu dot org 2007-09-06 01:32
---
Subject: Bug 33225
Author: jvdelisle
Date: Thu Sep 6 01:32:11 2007
New Revision: 128173
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128173
Log:
2007-09-06 Jerry DeLisle <[EMAI
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-09-07 17:54
---
Harold,
As a work around, try putting a LF at the end of the last line of the input
file. I am honing on on this, but don't have it yet.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33307
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-09-07 20:16
---
Subject: Bug 33307
Author: jvdelisle
Date: Fri Sep 7 20:16:05 2007
New Revision: 128253
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128253
Log:
2007-09-07 Jerry DeLisle <[EMAI
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-09-07 20:23
---
Subject: Bug 33307
Author: jvdelisle
Date: Fri Sep 7 20:23:40 2007
New Revision: 128254
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128254
Log:
2007-09-07 Jerry DeLisle <[EMAI
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2007-09-07 20:27
---
Fixed on trunk.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33307
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-09-08 20:16
---
This one is already reported.
*** This bug has been marked as a duplicate of 29835 ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-09-08 20:16
---
*** Bug 8 has been marked as a duplicate of this bug. ***
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-09-20 03:25
---
Un-assigning myself. No time at the moment
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-09-20 03:33
---
I am investigating.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-09-20 03:36
---
I will have a look.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-09-28 03:10
---
I have reverted the offending patch and will reopen pr33253, the least of the
two evils. This is one of those bugs where the fix for one breaks the other.
I am still trying to puzzle it out.
--
jvdelisle at
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-09-28 02:57
---
Subject: Bug 33421
Author: jvdelisle
Date: Fri Sep 28 02:57:41 2007
New Revision: 128857
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128857
Log:
2007-09-27 Jerry DeLisle <[EMAI
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2007-09-28 03:16
---
Reverted the patch to close pr33421. Reopening this to find the right
solution.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-09-28 16:56
---
Fixed on trunk
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-09-28 16:55
---
Subject: Bug 33400
Author: jvdelisle
Date: Fri Sep 28 16:55:07 2007
New Revision: 128868
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128868
Log:
2007-09-28 Jerry DeLisle <[EMAI
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2007-09-30 01:58
---
It turns out that the original patch for this bug is probably what we want.
Unfortunately it uncovers a nasty latent bug where an extraneous namelist read
is attempted. It only seems to occur with multiple
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-09-30 14:37
---
Subject: Bug 33400
Author: jvdelisle
Date: Sun Sep 30 14:36:40 2007
New Revision: 128892
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128892
Log:
2007-09-30 Jerry DeLisle <[EMAI
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-10-01 14:44
---
What does it do with -fno-range-check?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33609
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2007-10-03 00:33
---
Subject: Bug 33253
Author: jvdelisle
Date: Wed Oct 3 00:33:09 2007
New Revision: 128973
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128973
Log:
2007-10-02 Jerry DeLisle <[EMAI
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-10-03 00:40
---
Subject: Bug 33253
Author: jvdelisle
Date: Wed Oct 3 00:39:58 2007
New Revision: 128975
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128975
Log:
2007-10-03 Jerry DeLisle <[EMAI
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2007-10-03 00:41
---
Fixed on trunk.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-10-03 04:51
---
I think the problem here is that in match_data_constant we never even attempt
to match the array specification. Using gfc_match_array_spec or
gfc_match_array_ref I can successfully match and get the information
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-10-04 03:06
---
This is not a bug. See the manual:
-ffree-line-length-n
Set column after which characters are ignored in typical free-form lines in
the source file. The default value is 132. n may be `none', meaning
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2007-10-04 15:57
---
Subject: Bug 33253
Author: jvdelisle
Date: Thu Oct 4 15:57:28 2007
New Revision: 129016
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129016
Log:
2007-10-04 Jerry DeLisle <[EMAI
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2007-10-04 16:02
---
Subject: Bug 33253
Author: jvdelisle
Date: Thu Oct 4 16:02:42 2007
New Revision: 129018
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129018
Log:
2007-10-04 Jerry DeLisle <[EMAI
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-10-04 23:27
---
Created an attachment (id=14298)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14298&action=view)
Rough draft patch
Here is a first cut at a patch. It does not successfully get the assignment
901 - 1000 of 3058 matches
Mail list logo
