public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/91300] Wrong runtime error message with allocate and errmsg=
       [not found] <bug-91300-4@http.gcc.gnu.org/bugzilla/>
@ 2020-11-26 22:14 ` anlauf at gcc dot gnu.org
  2022-05-28 20:26 ` anlauf at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2020-11-26 22:14 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #6 from anlauf at gcc dot gnu.org ---
Currently the only generated STAT code is 5014 for LIBERROR_ALLOCATION.
This is ambiguous.

Shall we add another enum value to libgfortran_error_codes, such as
LIBERROR_VIRTUAL_MEMORY, LIBERROR_MEMORY, or LIBERROR_ALLOCATED?

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bug fortran/91300] Wrong runtime error message with allocate and errmsg=
       [not found] <bug-91300-4@http.gcc.gnu.org/bugzilla/>
  2020-11-26 22:14 ` [Bug fortran/91300] Wrong runtime error message with allocate and errmsg= anlauf at gcc dot gnu.org
@ 2022-05-28 20:26 ` anlauf at gcc dot gnu.org
  2022-05-30 20:32 ` cvs-commit at gcc dot gnu.org
  2022-05-30 20:58 ` anlauf at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-05-28 20:26 UTC (permalink / raw)
  To: gcc-bugs

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |anlauf at gcc dot gnu.org
                 CC|                            |anlauf at gcc dot gnu.org

--- Comment #7 from anlauf at gcc dot gnu.org ---
Patch submitted: https://gcc.gnu.org/pipermail/fortran/2022-May/057887.html

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bug fortran/91300] Wrong runtime error message with allocate and errmsg=
       [not found] <bug-91300-4@http.gcc.gnu.org/bugzilla/>
  2020-11-26 22:14 ` [Bug fortran/91300] Wrong runtime error message with allocate and errmsg= anlauf at gcc dot gnu.org
  2022-05-28 20:26 ` anlauf at gcc dot gnu.org
@ 2022-05-30 20:32 ` cvs-commit at gcc dot gnu.org
  2022-05-30 20:58 ` anlauf at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-05-30 20:32 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:871dbb6112e22ff92914613c332944fd19dd39a8

commit r13-858-g871dbb6112e22ff92914613c332944fd19dd39a8
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Sat May 28 22:02:20 2022 +0200

    Fortran: improve runtime error message with ALLOCATE and ERRMSG= [PR91300]

    ALLOCATE: generate different STAT,ERRMSG results for failures from
    allocation of already allocated objects or insufficient virtual memory.

    gcc/fortran/ChangeLog:

            PR fortran/91300
            * libgfortran.h: Define new error code LIBERROR_NO_MEMORY.
            * trans-stmt.cc (gfc_trans_allocate): Generate code for setting
            ERRMSG depending on result of STAT result of ALLOCATE.
            * trans.cc (gfc_allocate_using_malloc): Use STAT value of
            LIBERROR_NO_MEMORY in case of failed malloc.

    gcc/testsuite/ChangeLog:

            PR fortran/91300
            * gfortran.dg/allocate_alloc_opt_15.f90: New test.

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bug fortran/91300] Wrong runtime error message with allocate and errmsg=
       [not found] <bug-91300-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2022-05-30 20:32 ` cvs-commit at gcc dot gnu.org
@ 2022-05-30 20:58 ` anlauf at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-05-30 20:58 UTC (permalink / raw)
  To: gcc-bugs

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #9 from anlauf at gcc dot gnu.org ---
Fixed for gcc-13.  Closing.

Thanks for the report!

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-05-30 20:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-91300-4@http.gcc.gnu.org/bugzilla/>
2020-11-26 22:14 ` [Bug fortran/91300] Wrong runtime error message with allocate and errmsg= anlauf at gcc dot gnu.org
2022-05-28 20:26 ` anlauf at gcc dot gnu.org
2022-05-30 20:32 ` cvs-commit at gcc dot gnu.org
2022-05-30 20:58 ` 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).