Questions about binutils (mainly AS/GAS) and additional site info

Questions about binutils (mainly AS/GAS) and additional site info

[peter]

Hello,

  I have started a GNU free documentation and end user help project  for 
GAS/AS at:

https://savannah.nongnu.org/projects/gas-user/

    One focus of the site is to provide detailed examples of *GAS/AS*
assembly programming, either directly via command line 'as' or
indirectly via gcc. Another focus of the site is to provide GAS/AS
end user assistence via FAQ and community mailing list and online forum 
interaction.
   Hopefully the site will gain usefulness in the coming months as more 
working samples are added by interested users.
    The site is a bit lame right now since I am still researching alternate 
code to post (anyone have info on the mac boot cycle?). There is also a 
mailing list there to discuss GAS/AS end user stuff.

    I have a few questions about the state of binutils and the documentation 
on the redhat site.

   First off I notice that the redhat docs sem to be more up to date for 
GAS/AS than the postscript doc that I have a link to at GNU.  Since redhat 
took over cygnus, is redhat now the new maintainer of binutils? Or, is 
redhats version of binutils just that, a version for redhat? (if it works for 
others then great)

   Second, how permanent are the redhat docs? Should I just link to them or
would I be better off downloading a tarball, if there is one, and maintaining 
a duplicate site?

	Next I am looking for additional information and perhaps participation
for and from people who are assembly programming for CPUs *OTHER THAN*
Intel X86. There is a lot of information on AT&T syntax for intel but not so 
many examples for other procs. If anyone has any samples or interesting links 
to post on the site I would be most indebted.

Thanks for your time and any info you can provide.

Peter Willis

Re: Questions about binutils (mainly AS/GAS) and additional site info

[Nick Clifton]

Hi Peter,

> I have started a GNU free documentation and end user help project  for 
> GAS/AS at:
> 
> https://savannah.nongnu.org/projects/gas-user/

Excellent news - I hope that it proves to be very popular.


> Since redhat took over cygnus, is redhat now the new maintainer of
> binutils?

No - in fact definitely not.  Red Hat contributes some resources to the
binutils project (namely the surces.redhat.com site) but it is NOT the
maintainer for binutils.  The binutils project is totally an FSF GNU
project.  Various contributors and maintainers of the project may
happen to work for Red Hat, but it is no way a Red Hat project.


> Or, is redhats version of binutils just that, a version for redhat?

Yes.  Red Hat has also put some effort into creating documentation for
the tools it sells to customers, so this is why they may currently be
more up to date than the postscript doc you mention.  It should be the
case however that the documentation in the sources (in texinfo format)
are the most up to date docs of all.


>    Second, how permanent are the redhat docs? Should I just link to
> them or would I be better off downloading a tarball, if there is
> one, and maintaining a duplicate site?

Hmm - they should be permanent, by why take any chances.  If you
download the tarball and include a link to the Red Hat site you will
have the best of both worlds.


Cheers
        Nick

Re: Questions about binutils (mainly AS/GAS) and additional site info

[Hans-Peter Nilsson]

On Mon, 10 Mar 2003, peter wrote:

> Hello,
>
>   I have started a GNU free documentation and end user help project  for
> GAS/AS at:
>
> https://savannah.nongnu.org/projects/gas-user/

Besides what Nick said, I'd like to say that it would be real
nice if some documentation could be contributed back into the
binutils documentation.  I can see the usefulness in a
collection of examples outside binutils docs and as a general
help-desk, but please consider documenting functionality in the
actual binutils documentation.

Best of luck.  I just hope you don't go x86-centric and write
something like ``";"  acts as a line separator character''.
(It is in fact different in different targets and where it's a
character starting a comment-line, you may not notice until you
try and run the program.)  That includes at least two targets
running GNU/Linux.  See glibc config and build machinery.  For
CPU docs, see <URL:http://gcc.gnu.org/readings.html>.

brgds, H-P