Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754557Ab3HETZl (ORCPT ); Mon, 5 Aug 2013 15:25:41 -0400 Received: from mail-ve0-f179.google.com ([209.85.128.179]:47319 "EHLO mail-ve0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754136Ab3HETZk (ORCPT ); Mon, 5 Aug 2013 15:25:40 -0400 MIME-Version: 1.0 In-Reply-To: <87siyo3qna.fsf@tassilo.jf.intel.com> References: <1375721715.22073.80.camel@gandalf.local.home> <87siyo3qna.fsf@tassilo.jf.intel.com> Date: Mon, 5 Aug 2013 12:25:39 -0700 X-Google-Sender-Auth: 5PYzgSrwjf082KL4ek7TsGp6010 Message-ID: Subject: Re: [RFC] gcc feature request: Moving blocks into sections From: Linus Torvalds To: Andi Kleen Cc: Steven Rostedt , LKML , gcc , Ingo Molnar , Mathieu Desnoyers , "H. Peter Anvin" , Thomas Gleixner , David Daney , Behan Webster , Peter Zijlstra Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 835 Lines: 21 On Mon, Aug 5, 2013 at 12:04 PM, Andi Kleen wrote: > Steven Rostedt writes: > > Can't you just use -freorder-blocks-and-partition? > > This should already partition unlikely blocks into a > different section. Just a single one of course. That's horrible. Not because of dwarf problems, but exactly because unlikely code isn't necessarily *that* unlikely, and normal unlikely code is reached with a small branch. Making it a whole different section breaks both of those. Maybe some "really_unlikely()" would make it ok. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/