From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. Date: Thu, 23 May 2013 13:50:33 +0100 Message-ID: <20130523125033.GP18614@n2100.arm.linux.org.uk> References: <519DCBEF.3090208@asianux.com> <201305231259.43750.arnd@arndb.de> <20130523112401.GO18614@n2100.arm.linux.org.uk> <201305231409.02359.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Catalin Marinas , Linux-sh list , Benjamin Herrenschmidt , Chen Gang , Heiko Carstens , "paulus@samba.org" , "H. Peter Anvin" , Michel Lespinasse , Hans-Christian Egtvedt , Linux-Arch , linux-s390@vger.kernel.org, Yoshinori Sato , Richard Weinberger , Helge Deller , the arch/x86 maintainers , "James E.J. Bottomley" , "mingo@redhat.com" , Geert Uytterhoeven , Frederic Weisbecker , Paul McKenney , =?iso-8859-1?Q?H=E5vard?= Skinnemoen , Ser To: Arnd Bergmann Return-path: In-Reply-To: <201305231409.02359.arnd@arndb.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org On Thu, May 23, 2013 at 02:09:02PM +0200, Arnd Bergmann wrote: > On Thursday 23 May 2013, Russell King - ARM Linux wrote: > > This is the problem you guys are missing - unreachable() means "we lose > > control of the CPU at this point". > > I'm absolutely aware of this. Again, the current behaviour of doing nothing > at all isn't very different from undefined behavior when you get when you > get to the end of a function returning a pointer without a "return" statement, > or when you return from a function that has determined that it is not safe > to continue. Running off the end of a function like that is a different kettle of fish. The execution path is still as the compiler intends - what isn't is that the data returned is likely to be random trash. That's _quite_ different from the CPU starting to execute the contents of a literal data pool.