linux-kernel - RE: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Apr 2015 03:02:21 +0000
From:	"Zhang, Sonic" <Sonic.Zhang@...log.com>
To:	Chen Gang <xili_gchen_5257@...mail.com>,
	"realmz6@...il.com" <realmz6@...il.com>,
	Richard Weinberger <richard.weinberger@...il.com>
CC:	"adi-buildroot-devel@...ts.sourceforge.net" 
	<adi-buildroot-devel@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [Adi-buildroot-devel] [Consult] blackfin: About one building
 break	issue for STACKTRACE

Hi Gang,

Please only use the GCC for Blackfin 2013R1 or 2014R1 from https://sourceforge.net/projects/adi-buildroot/files/ . Upstream GCC5 isn't ported to Blackfin properly.

Regards,

Sonic

>-----Original Message-----
>From: Chen Gang [mailto:xili_gchen_5257@...mail.com]
>Sent: Thursday, April 16, 2015 11:22 PM
>To: realmz6@...il.com; Richard Weinberger
>Cc: adi-buildroot-devel@...ts.sourceforge.net; linux-kernel@...r.kernel.org
>Subject: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE
>
>Hello Maintainers:
>
>I want to consult one building issue about blackfin, the related issue
>is:
>
>    CC      arch/blackfin/kernel/stacktrace.o
>  arch/blackfin/kernel/stacktrace.c: In function 'save_stack_trace':
>  arch/blackfin/kernel/stacktrace.c:23:6: error: frame pointer required, but reserved
>   void save_stack_trace(struct stack_trace *trace)
>        ^
>  arch/blackfin/kernel/stacktrace.c:13:24: note: for 'current_frame_pointer'
>   register unsigned long current_frame_pointer asm("FP");
>                          ^
>
>For me:
>
> - Originally, I treated it as gcc's issue, but after think of, for me,
>   gcc is OK:
>
>    "-fomit-frame-pointer" is needed by extern "FP" pointer.
>
>    "-fomit-frame-pointer" is against "-pg" (they can not be together).
>
> - For kernel:
>
>    STACKTRACE needs "-fomit-frame-pointer", and FUNCTION_TRACER will
>    enable "-pg",
>
>    FUNCTION_TRACER and STACKTRACE are related.
>
>    The related commit: "1c873be Blackfin: initial support for ftrace"
>    (the commit time point is Jun 9 2009).
>
> - After this related commit, it never can pass building by upstream
>   blackfin gcc5:
>
>    make defconfig && make menuconfig
>
>    enable FUNCTION_TRACER (which also enable STACKTRACE)
>
>    make (which will cause building break)
>
>So I want to consult:
>
> - Is it OK to use upstream gcc5 for blackfin? (or which gcc version is
>   suitable for building blackfin Linux kernel?)
>
> - Did the original commit pass building ? (e.g. by one of old gcc
>   version).
>
> - How to fix this issue, next?
>
>
>Welcome any members ideas, suggestions and completions.
>
>Thanks.
>--
>Chen Gang
>
>Open, share, and attitude like air, water, and life which God blessed
>
>------------------------------------------------------------------------------
>BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN
>2 standard Learn Process modeling best practices with Bonita BPM through live exercises
>http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>_______________________________________________
>Adi-buildroot-devel mailing list
>Adi-buildroot-devel@...ts.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/adi-buildroot-devel

--
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/