--- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-08-17 13:10
---
Fixed.
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSI
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2007-08-17 13:09
---
Subject: Bug 33079
Author: fxcoudert
Date: Fri Aug 17 13:09:23 2007
New Revision: 127584
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127584
Log:
PR fortran/33079
* intrinsics/string_in
--- Comment #4 from patchapp at dberlin dot org 2007-08-16 13:25 ---
Subject: Bug number PR33079
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01012.html
--
http://gcc.gnu.org/bugzilla/sh
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
URL||http://gcc.gnu.org/ml/gcc-
|
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2007-08-15 14:22
---
(In reply to comment #2)
> Why do you need to special case len == 0? The other strings aren't NUL
> terminated either.
The zero-termination is just a detail to avoid keeping memory uninitialized.
The thing is th
--- Comment #2 from schwab at suse dot de 2007-08-15 14:18 ---
Why do you need to special case len == 0? The other strings aren't NUL
terminated either.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33079
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-08-15 14:05
---
The problem is shared by the TRIM and MIN/MAX. It is demonstrated by:
character(len=1) :: s
character(len=0) :: s0
s = " "
s0 = ""
call bar ("")
call bar (s)
call bar (s0)
call bar (trim(s))
cal
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Ke
