--- Comment #7 from domob at gcc dot gnu dot org 2008-06-18 13:56 ---
Committed patch and fixed as rev 136894.
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from domob at gcc dot gnu dot org 2008-06-18 13:56 ---
Fixed.
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED
--- Comment #9 from domob at gcc dot gnu dot org 2008-06-21 07:59 ---
(In reply to comment #8)
> I just downloaded the latest trunk version, which is
>
> GNU Fortran (GCC) 4.4.0 20080616 (experimental) [trunk revision 136838]
> Copyright (C) 2008 Free Software Foundat
--- Comment #6 from domob at gcc dot gnu dot org 2008-07-12 11:27 ---
Subject: Bug 33221
Author: domob
Date: Sat Jul 12 11:26:50 2008
New Revision: 137737
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137737
Log:
2008-07-12 Daniel Kraft <[EMAI
--- Comment #2 from domob at gcc dot gnu dot org 2008-07-19 09:38 ---
I want to work on this and started experimenting... Consider this test:
! ASINH is an intrinsic function as of F2008, not before.
! XXX: I hope so...
REAL FUNCTION asinh (arg)
IMPLICIT NONE
REAL :: arg
! Do
--- Comment #4 from domob at gcc dot gnu dot org 2008-07-21 10:02 ---
Created an attachment (id=15935)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15935&action=view)
Proposed test cases
Here's a set of test-cases (as diff) as I plan to fix this bug (dg-format ma
--- Comment #6 from domob at gcc dot gnu dot org 2008-07-21 12:17 ---
(In reply to comment #5)
> For the "INTRINSIC :: " error, one could consider mentioning
> "-fall-intrinsics"
> in the error message.
I'll do so (as I already do in the warning me
--- Comment #2 from domob at gcc dot gnu dot org 2008-07-22 17:06 ---
Subject: Bug 29835
Author: domob
Date: Tue Jul 22 17:05:55 2008
New Revision: 138063
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138063
Log:
2008-07-22 Daniel Kraft <[EMAIL PROTECTED]&g
--- Comment #3 from domob at gcc dot gnu dot org 2008-07-22 17:11 ---
The message locus for constant-string is not yet perfect, but the effort to
benefit ratio in this case is probably rather bad, so I mark this as fixed.
In my commit, I changed the "Unexpected element"
--- Comment #4 from domob at gcc dot gnu dot org 2008-07-24 16:31 ---
This seems to be still in there... Any interest that I work on this? What's
about emitting a warning if either len= or a substring-reference expression is
of a KIND that can have larger values than the machin
--- Comment #2 from domob at gcc dot gnu dot org 2008-07-24 17:03 ---
Isn't this maybe a general problem about optional string arguments? Or is this
really a eoshift-specific problem? I'm just thinking about a general solution
for this kind of problem if it isn't;
--- Comment #8 from domob at gcc dot gnu dot org 2008-07-24 18:53 ---
Subject: Bug 33141
Author: domob
Date: Thu Jul 24 18:52:51 2008
New Revision: 138122
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138122
Log:
2008-07-24 Daniel Kraft <[EMAIL PROTECTED]&g
--- Comment #9 from domob at gcc dot gnu dot org 2008-07-24 19:16 ---
Resolving fixed, discussion on better option names and minor changes welcome :)
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from domob at gcc dot gnu dot org 2008-07-25 17:13 ---
Hm... The tree I used for this check-in seems not to produce the crash, but my
current working-copy for finalization (updated last yesterday evening) shows it
(GNU/Linux-x86-32).
I will try to find out more on this
--- Comment #4 from domob at gcc dot gnu dot org 2008-07-25 18:28 ---
New status, I did update my other tree (unpatched) to the latest SVN, and
couldn't reproduce the problem there. Maybe I messed something up or the
problem occurs not "unconditionally"... With the pa
--- Comment #4 from domob at gcc dot gnu dot org 2008-07-28 18:41 ---
Thanks for all the hints, Tobias! I've had a look through the F2003 standard
about intrinsics taking optional char arguments, and it seems as though PACK
and RESHAPE would suffer from the same problem as EOSHIFT
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |domob at gcc dot gnu dot org
|dot org
--- Comment #6 from domob at gcc dot gnu dot org 2008-07-29 09:12 ---
Subject: Bug 36403
Author: domob
Date: Tue Jul 29 09:11:51 2008
New Revision: 138234
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138234
Log:
2008-07-29 Daniel Kraft <[EMAIL PROTECTED]&g
--- Comment #7 from domob at gcc dot gnu dot org 2008-07-29 09:17 ---
Fixed.
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #1 from domob at gcc dot gnu dot org 2008-07-31 10:31 ---
So the following two lines should give this error, right:
subroutine test (a)
character(len(a)) :: a
end subroutine test
subroutine test2 (n, arr)
integer :: arr(n), n
end subroutine test2
where in test2
--- Comment #3 from domob at gcc dot gnu dot org 2008-07-31 11:54 ---
Thanks for the quick reply, Tobias. I'll try to get the "used but not yet
typed" part implemented to emit errors for -std != gnu.
To fix the problem in this PR, I see those possible solutions:
a) D
--
domob at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |domob at gcc dot gnu dot org
|dot org
301 - 322 of 322 matches
Mail list logo
