discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] configure tests?


From: Eric Blossom
Subject: Re: [Discuss-gnuradio] configure tests?
Date: Fri, 26 May 2006 20:09:38 -0700
User-agent: Mutt/1.5.9i

On Fri, May 26, 2006 at 10:38:21PM -0400, Michael Dickens wrote:
> On May 26, 2006, at 8:52 PM, Eric Blossom wrote:
> >There's already a test in the usrp and gr-usrp code for this.
> >See configure.ac, AC_C_BIGENDIAN.
> 
> Yup, that works.  I'll send diff's once I have confirmation that this 
> is the issue.

Great.

> >  in test.asm (syntax could be wrong...)
> >
> >     .globl _start_test, _end_test
> >
> >     .align  16
> >  _start_test:
> >     .db     1
> >        .align  4
> >  _end_test:
> >
> >Then use nm to extract the resulting symbol values, followed by some
> >python, etc to compute difference.
> 
> Yes, something like that, but '.align 16' is too big.  sed could do  
> the trick too.

By too big, do you mean that some tool complains?


> Even simpler would be:
> +++++++++++++++++
>       .text
>       .globl  _abc
>       .byte   1
>       .align  4
> _abc:
> +++++++++++++++++
> Then:
> 
> gcc -c -o test.o test.S
> nm test.o | grep abc | sed -e 's/.*\([0-9a-fA-F][0-9a-fA-F]\).*abc.*/ 
> \1/'
> 
> the output of the NM pipe should be '10' or '16' for 'log' based and  
> something else (I think '04') for linear based.  This works for me  
> (returns '10', which is in hex but that doesn't matter).  Should be  
> pretty straight forward to stick in an m4 file. - MLD

Sounds good!

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]