linux-kernel - [3.7-rc6/perf,x86] Build failure at p6

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 for Android: free password hash cracker in your pocket

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

Message-Id: <201211171754.JCB26528.JLOFMFQOOFtVHS@I-love.SAKURA.ne.jp>
Date:	Sat, 17 Nov 2012 17:54:16 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	sfr@...b.auug.org.au
Cc:	a.p.zijlstra@...llo.nl, mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: [3.7-rc6/perf,x86] Build failure at p6_pmu declaration.

Commit caaa8be3 "perf, x86: Fix __initconst vs const" causes

  arch/x86/kernel/cpu/perf_event_p6.c:200: error: p6_pmu causes a section type conflict
  make[3]: *** [arch/x86/kernel/cpu/perf_event_p6.o] Error 1

error. Patching

  -static __initconst const struct x86_pmu p6_pmu = {
  +static __initconst struct x86_pmu p6_pmu = {

solved the error. But is this rather a compiler bug? I'm using gcc 3.3.5.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/