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

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

[debbugs-tracker] bug#23640: closed (25.1.50; Getting rid of compiler wa


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#23640: closed (25.1.50; Getting rid of compiler warnings)
Date: Tue, 31 May 2016 00:13:02 +0000

Your message dated Mon, 30 May 2016 20:11:53 -0400
with message-id <address@hidden>
and subject line Re: bug#23640: 25.1.50; Getting rid of compiler warnings
has caused the debbugs.gnu.org bug report #23640,
regarding 25.1.50; Getting rid of compiler warnings
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23640: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23640
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.1.50; Getting rid of compiler warnings Date: Sat, 28 May 2016 14:40:36 -0400 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
Building master on Cygwin with gcc-5.3.0 yields many "control reaches
end of non-void function" warnings.  What's the best way to get rid of
these?  Should I add return statements that will never be reached, like
this?

--- a/src/frame.c
+++ b/src/frame.c
@@ -263,6 +263,8 @@ See also `frame-live-p'.  */)
       return Qns;
     default:
       emacs_abort ();
+      /* Pacify compiler.  */
+      return Qnil;
     }
 }

Ken



--- End Message ---
--- Begin Message --- Subject: Re: bug#23640: 25.1.50; Getting rid of compiler warnings Date: Mon, 30 May 2016 20:11:53 -0400 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
On 5/30/2016 7:29 PM, Paul Eggert wrote:
The tradition of hijacking the symbol 'lint' for GCC purposes has been
used for many years in several GNU packages. As the problem you mention
affects only optionally-generated warnings on non-GNU platforms, I
suspect nobody has cared until now about the issue. Anyway, I changed
Emacs master to use the symbol GCC_LINT instead; this should avoid the
collision in names.

Thanks.  Closing.

Ken


--- End Message ---

reply via email to

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