public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/57611] New: [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90)
@ 2013-06-14 15:47 burnus at gcc dot gnu.org
  2013-06-27  9:25 ` [Bug fortran/57611] " dominiq at lps dot ens.fr
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-06-14 15:47 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57611

            Bug ID: 57611
           Summary: [Fortran-Dev Regression] Too much memory allocated
                    (gfortran.dg/coarray_lib_alloc_2.f90)
           Product: gcc
           Version: fortran-dev
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
            Blocks: 56818

The following should be:
  yy._data.base_addr = (void * restrict) __builtin_malloc (1);
however, it is
  yy._data.base_addr = (void * restrict) __builtin_malloc (128);

type t
end type t
class(t), allocatable :: yy(:)
allocate(yy(2))
end

Similarly for coarrays, cf. gfortran.dg/coarray_lib_alloc_2.f90:
 class(t), allocatable :: xx[:], yy(:)[:]
 allocate(yy(2)[*], stat=stat, errmsg=errmsg)
which gives
  xx._data.base_addr = _gfortran_caf_register (72, 1, &xx._data.token, &stat.0,
                                               &errmsg, 200);
  yy._data.base_addr = _gfortran_caf_register (192, 1, &yy._data.token,
&stat.2,
                                               &errmsg, 200);
The first arguments should be "1" instead of 72/192.


As the email at http://gcc.gnu.org/ml/fortran/2013-06/msg00071.html indicates,
there seems to be some pointer involved as the size varies between 32 and 64
bit systems.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/57611] [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90)
  2013-06-14 15:47 [Bug fortran/57611] New: [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90) burnus at gcc dot gnu.org
@ 2013-06-27  9:25 ` dominiq at lps dot ens.fr
  2021-12-18  2:09 ` pinskia at gcc dot gnu.org
  2023-04-08 18:37 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-27  9:25 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57611

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-06-27
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/57611] [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90)
  2013-06-14 15:47 [Bug fortran/57611] New: [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90) burnus at gcc dot gnu.org
  2013-06-27  9:25 ` [Bug fortran/57611] " dominiq at lps dot ens.fr
@ 2021-12-18  2:09 ` pinskia at gcc dot gnu.org
  2023-04-08 18:37 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-18  2:09 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57611

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I can't reproduce this even in GCC 4.9.4.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/57611] [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90)
  2013-06-14 15:47 [Bug fortran/57611] New: [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90) burnus at gcc dot gnu.org
  2013-06-27  9:25 ` [Bug fortran/57611] " dominiq at lps dot ens.fr
  2021-12-18  2:09 ` pinskia at gcc dot gnu.org
@ 2023-04-08 18:37 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2023-04-08 18:37 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57611

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
                 CC|                            |anlauf at gcc dot gnu.org
             Status|NEW                         |RESOLVED

--- Comment #3 from anlauf at gcc dot gnu.org ---
Also can't reproduce.  Closing.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-04-08 18:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-14 15:47 [Bug fortran/57611] New: [Fortran-Dev Regression] Too much memory allocated (gfortran.dg/coarray_lib_alloc_2.f90) burnus at gcc dot gnu.org
2013-06-27  9:25 ` [Bug fortran/57611] " dominiq at lps dot ens.fr
2021-12-18  2:09 ` pinskia at gcc dot gnu.org
2023-04-08 18:37 ` anlauf at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).