emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#51172: closed (Fix null-dereference warnings when compiling Emacs wi


From: GNU bug Tracking System
Subject: bug#51172: closed (Fix null-dereference warnings when compiling Emacs with GCC)
Date: Wed, 13 Oct 2021 18:50:02 +0000

Your message dated Wed, 13 Oct 2021 11:49:38 -0700
with message-id <fa7a6bb8-92a8-d8f3-52b6-e1b4314dc013@cs.ucla.edu>
and subject line Re: bug#51172: Fix null-dereference warnings when compiling 
Emacs with GCC
has caused the debbugs.gnu.org bug report #51172,
regarding Fix null-dereference warnings when compiling Emacs with GCC
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
51172: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=51172
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Fix null-dereference warnings when compiling Emacs with GCC Date: Tue, 12 Oct 2021 17:34:11 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 The attached patch against emacs-28 suppresses the final remaining GCC 11.2.1 diagnostics that are emitted after emacs-28 is configured with --enable-gcc-warnings on x86-64.

The patch is benign, and it's conceivable that changing xmalloc etc. to always return nonnull fixes unlikely and obscure bugs (though I haven't checked this). However, I didn't install the patch into the emacs-28 branch on the off-chance that Eli would prefer this sort of thing to be installed into the master branch.

Attachment: 0001-Pacify-GCC-Wanalyzer-possible-null-dereference.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#51172: Fix null-dereference warnings when compiling Emacs with GCC Date: Wed, 13 Oct 2021 11:49:38 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
On 10/13/21 5:14 AM, Eli Zaretskii wrote:

Yes, please install on master.

Thanks, done, and closing the bug report. I also got another diagnostic in the master branch, and fixed that in a separate commit.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]