avr-libc-dev
[Top][All Lists]
Advanced

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

Re: [avr-libc-dev] [RFC] faq update


From: Theodore A. Roth
Subject: Re: [avr-libc-dev] [RFC] faq update
Date: Wed, 11 Sep 2002 13:52:43 -0700 (PDT)

On Wed, 11 Sep 2002, Joerg Wunsch wrote:

:) > +Example:
:) > +
:) > +\verbatim
:) > +  $ avr-as -mmcu=atmega128 --gstabs -o foo.o foo.S
:) > +\endverbatim
:) > +
:)
:) Hmm, that should IMHO be "foo.s" (small .s).  Files ending in .S are
:) meant to be passed through cpp first, while files ending in .s are
:) going directly to the assembler.  Of course, this only applies to
:) (file) systems that differentiate between both cases, and only if
:) you use avr-gcc to make the distinction.  (That's why the -x
:) assembler-with-cpp made it into many CFLAGS, thought it's only
:) needed on non-Unix systems.)

I used .S since that is what is used for the asm files in the lib source.
My impression was that .s files are the intermediate files that gcc
produces (thus having gone through cpp) and then passes off to gas.

Ok. Looking at the build, avr-libc never uses avr-as directly. Looking at
the docs for avr-as, it seems that the only way to preprocess the .S files
is by sending them through avr-gcc with the "-x assembler-with-cpp"
option. Should this be noted in the dox, and if so, where?

Committed with s/foo.S/foo.s/ for asm example command.

Ted Roth





reply via email to

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