linux-kernel - Re: [PATCH] MIPS: Enable GCOV

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20201204120852.GE10011@alpha.franken.de>
Date:   Fri, 4 Dec 2020 13:08:52 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Xingxing Su <suxingxing@...ngson.cn>
Cc:     Youling Tang <tangyouling@...ngson.cn>, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Enable GCOV

On Thu, Dec 03, 2020 at 03:22:51PM +0800, Xingxing Su wrote:
> Enable gcov profiling of the entire kernel on mips. Required changes
> include disabling profiling for:
> 
> * arch/kernel/boot/compressed: not linked to main kernel.
> 
> Lightly tested on Loongson 3A3000 an 3A4000, seems to work as expected.
> 
> without "GCOV_PROFILE := n" in compressed Makefile,
> build errors as follows:
> ...
> ld: arch/mips/boot/compressed/string.o:(.data+0x88):
>  undefined reference to `__gcov_merge_add'
> ld: arch/mips/boot/compressed/string.o:
>  in function `_GLOBAL__sub_I_00100_0_memcpy':
> string.c:(.text.startup+0x4): undefined reference to `__gcov_init'
> ld: arch/mips/boot/compressed/string.o:
>  in function `_GLOBAL__sub_D_00100_1_memcpy':
> string.c:(.text.exit+0x0): undefined reference to `__gcov_exit'
> ...
> 
> Signed-off-by: Youling Tang <tangyouling@...ngson.cn>
> Signed-off-by: Xingxing Su <suxingxing@...ngson.cn>
> ---
>  arch/mips/Kconfig                  | 1 +
>  arch/mips/boot/compressed/Makefile | 1 +
>  2 files changed, 2 insertions(+)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]