Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759630AbbKUKOO (ORCPT ); Sat, 21 Nov 2015 05:14:14 -0500 Received: from pandora.arm.linux.org.uk ([78.32.30.218]:44928 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751321AbbKUKOL (ORCPT ); Sat, 21 Nov 2015 05:14:11 -0500 Date: Sat, 21 Nov 2015 10:13:50 +0000 From: Russell King - ARM Linux To: Stephen Boyd Cc: linux-arm-kernel@lists.infradead.org, =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= , Arnd Bergmann , Nicolas Pitre , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [RFC/PATCH 2/3] recordmcount: Record locations of __aeabi_{u}idiv() calls on ARM Message-ID: <20151121101349.GI8644@n2100.arm.linux.org.uk> References: <1448068997-26631-1-git-send-email-sboyd@codeaurora.org> <1448068997-26631-3-git-send-email-sboyd@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448068997-26631-3-git-send-email-sboyd@codeaurora.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1553 Lines: 36 On Fri, Nov 20, 2015 at 05:23:16PM -0800, Stephen Boyd wrote: > @@ -452,14 +631,14 @@ static char const * > __has_rel_mcount(Elf_Shdr const *const relhdr, /* is SHT_REL or SHT_RELA */ > Elf_Shdr const *const shdr0, > char const *const shstrtab, > - char const *const fname) > + char const *const fname, const char *find) > { > /* .sh_info depends on .sh_type == SHT_REL[,A] */ > Elf_Shdr const *const txthdr = &shdr0[w(relhdr->sh_info)]; > char const *const txtname = &shstrtab[w(txthdr->sh_name)]; > > - if (strcmp("__mcount_loc", txtname) == 0) { > - fprintf(stderr, "warning: __mcount_loc already exists: %s\n", > + if (strcmp(find, txtname) == 0) { > + fprintf(stderr, "warning: %s already exists: %s\n", find, Oh, it's this which has been spewing that silly "warning: __mcount_loc already exists" message thousands of times in my nightly kernel builds (so much so, that I've had to filter the thing out of the logs.) Given that this is soo noisy, I think first we need to get to the bottom of why this program is soo noisy before we try to make it more functional. I had assumed that this message was produced by something in the toolchain, not something in the kernel. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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/