This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Invalid asms in libstdc++-v3/config/cpu/alpha/bits/atomicity.h
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: Invalid asms in libstdc++-v3/config/cpu/alpha/bits/atomicity.h
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Wed, 24 Jan 2001 16:06:48 -0500
- Cc: libstdc++ at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org
- References: <orelxtvboa.fsf@guarana.lsd.ic.unicamp.br>
On Wed, Jan 24, 2001 at 02:03:49AM -0200, Alexandre Oliva wrote:
> Tru64's assembler can't grasp /**/ comments, .subsection nor
> .previous. I suppose this was grabbed from glibc...
Hmmmm. This has come up once before. We should be okay with /**/...
here's the chapter on comments from the Tru64 assembler manual:
# 2.2 Comments
#
# The number sign character (#) introduces a comment. Comments that
# start with a number sign extend through the end of the line on which
# they appear. You can also use C language notation (/*...*/) to delimit
# comments.
#
# Do not start a comment with a number sign in column one; the assembler
# uses cpp (the C language preprocessor) to preprocess assembler code
# and cpp interprets number signs in the first column as preprocessor
# directives.
> We can obviously remove the comments, but I don't see the point of
> using .subsection and .previous, and I'm not sure 1b and 2f are
> supported either.
Check out
http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html#3_3
More specifically, check out the email thread linked to from there.
The manual quote above was taken from the manual linked to from the email.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.