[Top][All Lists]

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

RE: [avr-gcc-list] error in inline assembler docu found at:http://www.no

From: Eric Weddington
Subject: RE: [avr-gcc-list] error in inline assembler docu found at:http://www.nongnu.org/avr-libc/user-manual/inline_asm.html
Date: Fri, 24 Aug 2007 14:14:40 -0600

> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Johannes Krude
> Sent: Friday, August 24, 2007 4:32 AM
> To: address@hidden
> Cc: address@hidden
> Subject: [avr-gcc-list] error in inline assembler docu found
> at:http://www.nongnu.org/avr-libc/user-manual/inline_asm.html
> hi,
> as the author of
> http://www.nongnu.org/avr-libc/user-manual/inline_asm.html
> stated:" a wrong documentation sometimes might be worse than
> none", this is
> definitly true for this documentation. I have spend a lot of
> time figuring
> out what I did wrong in my program until i finaly found out
> the error was in
> the documentation. Unfortunately all docus for avr-gcc inline
> assembler found
> first on google do it wrong.
> The documentation stats: "The linefeed and tab characters
> will make the
> assembler listing generated by the compiler more readable",
> this is far from
> the truth, instead the compiler relies on the linefeed and
> tabs. If you omit
> the linefeeds and tabs the compiler complains about: "garbage
> at end of line"
> There is an important point missing about the input and
> output operands. IO
> registers always have to be input operands, even if you only
> use them as
> output. Otherwise the compiler wails about: "invalid lvalue
> in asm statement"
> I don't read tihs list so don't expect me to answer if you
> don't write to me
> personaly.
> In hope of making the world a little better, johannes

Thanks for the feedback on this. Yes, the inline assembler documentation
needs some updating. We've had other bug reports for the docs as well.

Can you please fill out a bug tracker at the avr-libc project on Savannah?:
Emails have a tendency to get lost and we don't want to forget this issue.

Eric Weddington


reply via email to

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