From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31288] 5.0: build fails with gcc 14x
Date: Wed, 24 Jan 2024 15:40:48 +0000 [thread overview]
Message-ID: <bug-31288-6586-9q2uN7Wswb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31288-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31288
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |wcohen at redhat dot com
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
The transposed calloc arguments were addressed by the recent git commits in
upstream systemtap:
commit 6c0b92b340db23ccc49e18007d4ecbdef3306bd6
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Thu Jan 18 16:37:39 2024 -0500
stapvirt.c: More gcc-14 -Werror=calloc-transposed-args compatibility
commit 52596f023652114642faba5726c99488529029ce
Author: Sergei Trofimovich <slyich@gmail.com>
Date: Thu Dec 21 10:00:06 2023 +0000
staprun: fix build against upcoming `gcc-14`
(`-Werror=calloc-transposed-args`)
`gcc-14` added a new `-Wcalloc-transposed-args` warning recently. It
detected minor infelicity in `calloc()` API usage in `systemtap`:
staprun.c: In function 'main':
staprun.c:550:50: error: 'calloc' sizes specified with 'sizeof' in the
earlier argument and not in the later argument [-Werror=calloc-transposed-args]
550 | char ** new_argv = calloc(sizeof(char
*),argc+2);
| ^~~~
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-01-24 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 8:24 [Bug runtime/31288] New: " kloczko.tomasz at gmail dot com
2024-01-24 15:40 ` wcohen at redhat dot com [this message]
2024-01-25 19:35 ` [Bug runtime/31288] " fche at redhat 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-31288-6586-9q2uN7Wswb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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).