lkml.org 
[lkml]   [2008]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: sparc64: Optimized immediate value implementation build error
From
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date: Fri, 3 Oct 2008 16:10:07 -0400

> I ran a cross-compiler on the -lttng tree
> git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git
>
> to build the sparc64 arch, and ran across this build error :
>
> /home/compudj/git/morestable/linux-2.6-lttng/include/trace/sched.h: In function `do_fork':
> /home/compudj/git/morestable/linux-2.6-lttng/include/trace/sched.h:38: warning: asm operand 1 probably doesn't match constraints
> /home/compudj/git/morestable/linux-2.6-lttng/include/trace/sched.h:38: error: impossible constraint in `asm'
> /home/compudj/git/morestable/linux-2.6-lttng/include/trace/sched.h:38: warning: 'value' might be used uninitialized in this function
> make[2]: *** [kernel/fork.o] Error 1
>
> I think it's caused by :
> http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=commit;h=c76bfa90a6eb02651368a152b3646aa672d9e625

It can't be "caused by" that commit because that's the initial
immediate value sparc64 support I wrote and the tree very much compiled
properly when I did test builds way back then.

I don't have time to look further into this right now, sorry.


\
 
 \ /
  Last update: 2008-10-13 10:19    [W:0.061 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site