public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hanzac at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24610]  New: The comment start symbol of arm target
Date: Tue, 01 Nov 2005 07:31:00 -0000	[thread overview]
Message-ID: <bug-24610-11002@http.gcc.gnu.org/bugzilla/> (raw)

It's true that the arm comment start symbol is '@', but GCC will generate some
assembler code end with a '@' and a comment without a separator so it can't be
parsed by gas.

For example, I compile the libgcc2.c:__gcc_bcmp with xgcc, it failed:
_____________________________________________________________________
/* Like bcmp except the sign is meaningful.
   Result is negative if S1 is less than S2,
   positive if S1 is greater, 0 if S1 and S2 are equal.  */

int
__gcc_bcmp (const unsigned char *s1, const unsigned char *s2, size_t size)
{
  while (size > 0)
    {
      const unsigned char c1 = *s1++, c2 = *s2++;
      if (c1 != c2)
        return c1 - c2;
      size--;
    }
  return 0;
}
_____________________________________________________________________
I'm compile gcc under cygwin and mingw32-gcc, binutils-2.16.1 already compiled
also with --target=arm-wince-pe, here is the gcc(gcc-4.1-20051022)
configuration:
$ ./configure --disable-nls --disable-win32-registry --enable-threads=win32
--host=i686-pc-mingw32 --build=i686-pc-mingw32 --target=arm-wince-pe

I also found that if I made a change in gcc-4.1-20051022\gcc\config\arm\aout.h
(add a semicolon), it will work:
@@ -294,7 +294,7 @@
 #endif

 #ifndef ASM_COMMENT_START
-#define ASM_COMMENT_START "@"
+#define ASM_COMMENT_START ";@"
 #endif

 /* This works for GAS and some other assemblers.  */

See also in: http://gcc.gnu.org/ml/gcc/2005-10/msg01215.html


-- 
           Summary: The comment start symbol of arm target
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hanzac at gmail dot com
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: arm-wince-pe


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24610


             reply	other threads:[~2005-11-01  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  7:31 hanzac at gmail dot com [this message]
2005-11-01  9:37 ` [Bug target/24610] " rearnsha at gcc dot gnu dot org
2005-11-02  6:27 ` hanzac at gmail dot com
2005-11-02 10:13 ` rearnsha at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-24610-11002@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).