--- Comment #10 from jb at gcc dot gnu dot org 2008-05-12 11:27 ---
>Time for a "what we want to fix with the new array descriptor"
>meta-PR?
I started a wiki page for this, with a few issues from the top of my head:
http://gcc.gnu.org/wiki/ArrayDescriptorUpdate
--
http://gcc.gnu.o
--- Comment #9 from tkoenig at gcc dot gnu dot org 2008-05-11 20:39 ---
Fixed on trunk.
I don't think this really needs to be fixed on 4.3, so
I am closing this.
--
tkoenig at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #8 from tkoenig at gcc dot gnu dot org 2008-05-11 20:29 ---
Subject: Bug 35719
Author: tkoenig
Date: Sun May 11 20:28:52 2008
New Revision: 135187
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=135187
Log:
2008-05-11 Thomas Koenig <[EMAIL PROTECTED]>
PR fo
--- Comment #7 from tkoenig at gcc dot gnu dot org 2008-05-09 18:34 ---
(In reply to comment #6)
> Another solution is to have status flags for allocated and associated in the
> descriptor, IIRC at least Pathscale does this.
>
> Aren't there actually free bits left in the dtype flag tha
--- Comment #6 from jb at gcc dot gnu dot org 2008-05-09 06:15 ---
Another solution is to have status flags for allocated and associated in the
descriptor, IIRC at least Pathscale does this.
Aren't there actually free bits left in the dtype flag that gfortran could use,
without requirin
--- Comment #5 from tkoenig at gcc dot gnu dot org 2008-05-06 21:24 ---
Created an attachment (id=15587)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15587&action=view)
Trial patch
Here's an attempt at a patch, which should do the
right thing at least for this case.
--
http:
--- Comment #4 from tkoenig at gcc dot gnu dot org 2008-05-05 18:24 ---
(In reply to comment #3)
> One possibility is to allocate something for zero-sized arrays, e.g. one
> element. The array bounds ensure than that the program still knows that the
> size of the array is zero. The extr
--- Comment #3 from burnus at gcc dot gnu dot org 2008-05-05 05:46 ---
(In reply to comment #2)
> The problem is that we set ila1 to a null pointer if its
> size is zero: [...]
> It isn't clear to me why we do this (maybe as a debugging aid?).
Well, if we don't assign anything, the memo
--- Comment #2 from tkoenig at gcc dot gnu dot org 2008-05-04 21:29 ---
The problem is that we set ila1 to a null pointer if its
size is zero:
D.647 = size.6 * 4;
if (D.647 < 0)
{
_gfortran_runtime_error (&"Attempt to allocate a negative amount of
memory."[1]{lb: 1
--- Comment #1 from burnus at gcc dot gnu dot org 2008-03-27 16:53 ---
Confirm. Thanks for finding this bug.
--
burnus at gcc dot gnu dot org changed:
What|Removed |Added
10 matches
Mail list logo
