public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/113793] malloc abort on character allocate with source argument
Date: Wed, 07 Feb 2024 19:35:15 +0000	[thread overview]
Message-ID: <bug-113793-4-zy6IR42tbE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113793-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gcc dot gnu.org
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-02-07
           Keywords|                            |wrong-code
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to Manfred Schwarb from comment #0)
> Allocating an allocatable character array, I get a malloc error
> when the source argument is not properly padded:
> 
>       CHARACTER*30,allocatable :: a(:),b(:)
>       ALLOCATE(a(100),source=" ")
>       ALLOCATE(b(100),source=" ")
>       END
> 
> yields:
> malloc(): corrupted top size

Confirmed.

> I would have expected that the source argument is automatically padded
> as with variable assignments and function call arguments.

The dump-tree shows that it is padded, but the actual malloc is too short:

            a.data = (void * restrict) __builtin_malloc (100);

Omitting the source= part, we get the expected:

            a.data = (void * restrict) __builtin_malloc (3000);

  reply	other threads:[~2024-02-07 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 23:28 [Bug fortran/113793] New: " manfred99 at gmx dot ch
2024-02-07 19:35 ` anlauf at gcc dot gnu.org [this message]
2024-02-07 22:09 ` [Bug fortran/113793] " anlauf at gcc dot gnu.org
2024-04-11 20:29 ` anlauf at gcc dot gnu.org
2024-04-12 20:28 ` anlauf at gcc dot gnu.org
2024-04-12 20:29 ` anlauf at gcc dot gnu.org
2024-04-13 18:04 ` anlauf at gcc dot gnu.org
2024-04-16 16:48 ` cvs-commit at gcc dot gnu.org
2024-04-16 18:59 ` anlauf 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-113793-4-zy6IR42tbE@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).