public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113634] New: FAIL: gcc.dg/Wfree-nonheap-object-7.c, incorrect declaration for calloc()
Date: Sun, 28 Jan 2024 07:45:24 +0000	[thread overview]
Message-ID: <bug-113634-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113634
           Summary: FAIL: gcc.dg/Wfree-nonheap-object-7.c, incorrect
                    declaration for calloc()
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Keywords: testsuite-fail
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nightstrike at gmail dot com
  Target Milestone: ---

This test uses an incorrect declaration for calloc():

void *calloc(long, long);

whereas the standard requires that it be:

void *calloc(size_t, size_t);


This can be replaced with:

void *calloc(__SIZE_TYPE__, __SIZE_TYPE__);

But I'd question why the test doesn't just include stdlib.h.  Or, if the intent
is to avoid including headers as much as possible, use __builtin_calloc(),
which does the right thing.  All three of these solutions work (header,
builtin, correct declaration).

             reply	other threads:[~2024-01-28  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  7:45 nightstrike at gmail dot com [this message]
2024-01-28  7:53 ` [Bug testsuite/113634] " pinskia 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-113634-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).