public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51073] New: _gfortran_caf_register incorrectly assumes malloc(0) returns non-NULL
Date: Thu, 10 Nov 2011 07:39:00 -0000 [thread overview]
Message-ID: <bug-51073-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51073
Bug #: 51073
Summary: _gfortran_caf_register incorrectly assumes malloc(0)
returns non-NULL
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: joel@gcc.gnu.org
Revision: Wed Nov 9 13:24:05 UTC 2011 (revision 181203)
Target: mips-rtems4.11 but impacts all where malloc(0) returns NULL
I am debugging why some of the gfortran tests are failing. I have tracked NN
failures down to this code in caf/mpi.c around line 155.
/* Token contains only a list of pointers. */
local = malloc (size);
token = malloc (sizeof (void*) * caf_num_images);
if (unlikely (local == NULL || token == NULL))
goto error;
>From http://pubs.opengroup.org/onlinepubs/009695399/functions/malloc.html
Upon successful completion with size not equal to 0, malloc() shall return a
pointer to the allocated space. If size is 0, either a null pointer or a unique
pointer that can be successfully passed to free() shall be returned. Otherwise,
it shall return a null pointer [CX] and set errno to indicate the error.
The code uses the memory pointed to by local to pass to MPI_Allgather() and
then returns it to the caller. I suspect that the line "local = malloc (size)"
should be something like:
local = malloc ((size == 0)? sizeof(XXX) : size);
Where XXX needs to be the type of one entity of sufficient size to pass into
MPI_Allgather.
next reply other threads:[~2011-11-10 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 7:39 joel at gcc dot gnu.org [this message]
2011-11-10 8:30 ` [Bug fortran/51073] " burnus at gcc dot gnu.org
2011-11-10 10:14 ` burnus at gcc dot gnu.org
2011-11-10 11:10 ` burnus at gcc dot gnu.org
2011-11-10 13:28 ` joel at gcc dot gnu.org
2011-11-10 13:39 ` burnus at gcc dot gnu.org
2011-11-10 18:02 ` joel at gcc dot gnu.org
2011-11-14 8:48 ` burnus at gcc dot gnu.org
2011-11-14 9:40 ` burnus at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-51073-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).