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-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
