From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6100 invoked by alias); 10 May 2010 14:53:46 -0000 Received: (qmail 6079 invoked by uid 48); 10 May 2010 14:53:35 -0000 Date: Mon, 10 May 2010 14:53:00 -0000 Message-ID: <20100510145335.6078.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/44053] "benchmark" function attribute. In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "svfuerst at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg00988.txt.bz2 ------- Comment #5 from svfuerst at gmail dot com 2010-05-10 14:53 ------- The problem is that the list of these workarounds tends to increase with each release of gcc. (i.e. noclone was added in gcc 4.5) It would be nice if there was a single attribute to use that would work with all future versions of the compiler, no matter how smart it gets. For example, putting the function to benchmark into a separate compilation unit isn't guaranteed to work indefinitely. If ever lto is enabled by default in the future, it will then cause problems. Think of it as the difference between "-O2", and the long list of command line optimization flags that -O2 represents. Eventually the complexity of adding that new flag is less than the complexity of the list of things it represents. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44053