public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112347] [14 regression] ICE on jemalloc-5.3.0: Segmentation fault around convert_for_assignment()
Date: Thu, 02 Nov 2023 18:58:59 +0000	[thread overview]
Message-ID: <bug-112347-4-1HiSDKRWdx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112347-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Martin Uecker <muecker at gwdg dot de> ---

In this case this is by design because the size of an element should be second
argument to calloc. ("The calloc function allocates space for an array of nmemb
objects, each of whose size is size.")

  parent reply	other threads:[~2023-11-02 18:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  9:49 [Bug c/112347] New: " slyfox at gcc dot gnu.org
2023-11-02  9:53 ` [Bug c/112347] " slyfox at gcc dot gnu.org
2023-11-02 10:00 ` slyfox at gcc dot gnu.org
2023-11-02 10:10 ` rguenth at gcc dot gnu.org
2023-11-02 10:24 ` muecker at gwdg dot de
2023-11-02 12:22 ` muecker at gwdg dot de
2023-11-02 12:24 ` muecker at gwdg dot de
2023-11-02 12:27 ` muecker at gwdg dot de
2023-11-02 12:33 ` dcb314 at hotmail dot com
2023-11-02 13:33 ` slyfox at gcc dot gnu.org
2023-11-02 13:55 ` cvs-commit at gcc dot gnu.org
2023-11-02 16:24 ` dcb314 at hotmail dot com
2023-11-02 18:58 ` muecker at gwdg dot de [this message]
2023-11-03  7:53 ` muecker at gwdg dot de
2023-11-03  9:54 ` dcb314 at hotmail dot com
2023-11-03 11:02 ` muecker at gwdg dot de
2023-11-03 11:06 ` dcb314 at hotmail dot com
2023-11-03 11:22 ` muecker at gwdg dot de
2023-11-03 11:55 ` sjames at gcc dot gnu.org
2023-11-03 12:12 ` muecker at gwdg dot de
2023-11-03 12:15 ` sjames at gcc dot gnu.org
2023-11-03 12:17 ` muecker at gwdg dot de
2023-11-04  8:22 ` dcb314 at hotmail dot com

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-112347-4-1HiSDKRWdx@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).