public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52554] Variable called $1 causes invalid asm to be generated
Date: Wed, 28 Mar 2012 06:09:00 -0000	[thread overview]
Message-ID: <bug-52554-4-YIT16Bd7VH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52554-4@http.gcc.gnu.org/bugzilla/>

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

Florian Weimer <fw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|accepts-invalid, wrong-code |
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |fw at gcc dot gnu.org
         Resolution|                            |INVALID

--- Comment #4 from Florian Weimer <fw at gcc dot gnu.org> 2012-03-28 05:38:56 UTC ---
Some platforms (such as VMS) support $ in identifiers, similar to _.  It seems
that your assembler doesn't:

http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html

(If you compile with -pedantic, you'll get a warning.)

This is not much different from platforms where global symbols are
case-insensitive or severely limited in length.


  parent reply	other threads:[~2012-03-28  5:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 21:29 [Bug c/52554] New: " rwxr-xr-x at gmx dot de
2012-03-12 13:28 ` [Bug c/52554] " rguenth at gcc dot gnu.org
2012-03-12 14:22 ` schwab@linux-m68k.org
2012-03-13 17:20 ` rwxr-xr-x at gmx dot de
2012-03-28  6:09 ` fw at gcc dot gnu.org [this message]
2012-03-28  9:45 ` [Bug target/52554] " webmaster at openhardware dot de
2012-03-29 11:44 ` rwxr-xr-x at gmx dot de
2012-03-29 13:42 ` webmaster at openhardware dot de
2012-04-04  3:38 ` rwxr-xr-x at gmx dot de
2021-07-29 23:46 ` pinskia at gcc dot gnu.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-52554-4-YIT16Bd7VH@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).