Are you thinking of this as a way to embedded assembly clearer? I am not a
great fan of using macro pairs that open or close scopes - I've made them
and used them myself before, and got confused by them. They can really mess
up bug-hunting when gcc reports a nesting error somewhere totally different
than the actual error, and they confuse debugging. gcc does such a good job
these days (especially with -O3) that there is not much call for assembly
for the sake of speed, and when using it to get extra functionality (like
"dadd"), then it is better to keep things short and simple.
>
> #define ASMSTART __asm__ __volatile__ (
> #define ASMEND );
> #define _(x...) #x"\n\t"
>
>
> int foo()
> {
> int aa;
>
> ASMSTART
>
> _( mov r1, r12 )
> _( clr %0 )
>
> : "=r" (aa)
>
> ASMEND
>
> return aa;
> }
>
>
>
> --
> /********************************************************************
> ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ
> `6_ 6 ) `-. ( ).`-.__.`) Enterprise Information Sys
> (_Y_.)' ._ ) `._ `. ``-..-' Nevsky prospekt, 20 / 44
> _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia
> (il),-'' (li),' ((!.-' +7 (812) 3468202, 5585314
> ********************************************************************/
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>
