From: Pip Cet <pipcet@protonmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org, "Gerd Möllmann" <gerd.moellmann@gmail.com>
Subject: Re: scratch/igc warning
Date: Wed, 26 Jun 2024 15:45:25 +0000 [thread overview]
Message-ID: <Nc4opNsz5h7Gu8Vci9j82rMk_Epxwr4JW3PEd__dbyQqYfrGqUJ2Z6JtYTC50SMr-fMJ9oJA1-v1_dTyQ7ysslYhaLdr0AaeZIqn8ZnWPEY=@protonmail.com> (raw)
In-Reply-To: <yp1r0cjn4s0.fsf@fencepost.gnu.org>
On Wednesday, June 26th, 2024 at 14:43, Andrea Corallo <acorallo@gnu.org> wrote:
> > Something in between: the code is trying to clear a struct partially by memsetting starting from a given offset to the end of the struct. However, it's not specific to the igc branch.
>
>
> I believe it is, I don't see it in my other builds.
I meant the issue, if there is one, isn't specific to the igc branch. The GCC warning appears to be specific to allocation functions not declared with the attributes provided by ATTRIBUTE_MALLOC_SIZE ((1)). If I remove that attribute from xmalloc on the master branch and enable fortification, I see the warning there, as well.
Pip
next prev parent reply other threads:[~2024-06-26 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 14:08 scratch/igc warning Andrea Corallo
2024-06-26 14:31 ` Pip Cet
2024-06-26 14:43 ` Andrea Corallo
2024-06-26 15:45 ` Pip Cet [this message]
2024-06-26 14:39 ` Gerd Möllmann
2024-06-26 14:48 ` Andrea Corallo
2024-06-26 14:57 ` Gerd Möllmann
2024-06-26 16:25 ` scratch/igc lread testsuite error [was Re: scratch/igc warning] Andrea Corallo
2024-06-26 16:35 ` Gerd Möllmann
2024-06-27 7:01 ` Helmut Eller
2024-06-27 7:09 ` Gerd Möllmann
2024-06-27 12:09 ` Andrea Corallo
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Nc4opNsz5h7Gu8Vci9j82rMk_Epxwr4JW3PEd__dbyQqYfrGqUJ2Z6JtYTC50SMr-fMJ9oJA1-v1_dTyQ7ysslYhaLdr0AaeZIqn8ZnWPEY=@protonmail.com' \
--to=pipcet@protonmail.com \
--cc=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).