https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
--- Comment #8 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:871dbb6112e22ff92914613c332944fd19dd39a8
commit r13-858-g871dbb6112e22ff92914613c332944fd19dd39a8
Author: Harald Anlauf
Date: Sat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|u
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_MEM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
--- Comment #5 from G. Steinmetz ---
Please ignore comment 4, wrong PR ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
G. Steinmetz changed:
What|Removed |Added
CC||gs...@t-online.de
--- Comment #4 from G.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
Bug 91300 depends on bug 68401, which changed state.
Bug 68401 Summary: improve 'Allocation would exceed memory limit'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68401
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
Janne Blomqvist changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
--- Comment #2 from zed.three at gmail dot com ---
Forgive me, but what is stupid here? The perceived wisdom is that it is best
practice to always use `stat` with `allocate`, and the addition of `errmsg` now
gives us something portable to hopefull
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P5
CC|
10 matches
Mail list logo
