Martín Ferrari wrote:
> On Mon, Dec 8, 2008 at 09:30, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>
> >> Could you tell me if the assembler code generated by gcc looks as a
> >> reasonable replacement for the offending code you've patched?
> >
> > I think __sync_lock_test_and_set should be good enoug
On Mon, Dec 8, 2008 at 09:30, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>> Could you tell me if the assembler code generated by gcc looks as a
>> reasonable replacement for the offending code you've patched?
>
> I think __sync_lock_test_and_set should be good enough, AFAICS there's
> no need to do
Martín Ferrari wrote:
> Hi,
>
> On Sun, Dec 7, 2008 at 14:21, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>
> >> as -o tas.o tas.s
> >> tas.s: Assembler messages:
> >> tas.s:10: Error: illegal operands `ori t1,zero,12345'
> >> tas.s:11: Error: opcode not supported on this processor: mips1 (mips1) `
Hi,
On Sun, Dec 7, 2008 at 14:21, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>> as -o tas.o tas.s
>> tas.s: Assembler messages:
>> tas.s:10: Error: illegal operands `ori t1,zero,12345'
>> tas.s:11: Error: opcode not supported on this processor: mips1 (mips1) `ll
>> t0,(a0)'
>> tas.s:12: Error: op
Package: drawterm
Version: 0.cvs+20080909-1
Severity: serious
Tags: patch
There was an error while trying to autobuild your package:
> Automatic build of drawterm_0.cvs+20080909-1 on ball by sbuild/mips 99.99
> Build started at 20081206-1246
[...]
> gcc -Wall -Wno-missing-braces -ggdb -I.. -I..
5 matches
Mail list logo
