public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/31782] Invalid assembly code on initial dollar signs
Date: Sun, 22 Jun 2014 11:27:00 -0000	[thread overview]
Message-ID: <bug-31782-4-pIsVed1baD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31782-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31782

--- Comment #7 from Harald van Dijk <harald at gigawatt dot nl> ---
That's good to know. Trying some more, clang does manage to get even weirder
symbol names right, because gas does have a form of quoting already, and clang
makes use of it.

int x __asm__(")");
int main() { return x; }

With clang, this works.

...
        movl    ")", %eax
...
        .type   ")",@object             # @")"
        .comm   ")",4,4
...

If it's simpler to implement, then instead of parenthesising, $ could
alternatively be treated as a symbol that needs quoting, which is a more
general solution that will work for any possible symbol name.


  parent reply	other threads:[~2014-06-22 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31782-4@http.gcc.gnu.org/bugzilla/>
2011-02-04 16:42 ` funto66 at gmail dot com
2014-06-22  8:42 ` raphael.jakse at gmail dot com
2014-06-22 11:27 ` harald at gigawatt dot nl [this message]
2014-06-23  7:25 ` raphael.jakse at gmail dot com
2014-06-23 21:36 ` harald at gigawatt dot nl
2014-06-24  7:37 ` raphael.jakse at gmail dot com
2021-07-29 23:45 ` pinskia at gcc dot gnu.org
2021-07-29 23:46 ` pinskia at gcc dot gnu.org
2021-07-29 23:46 ` pinskia at gcc dot gnu.org
2021-08-03  1:18 ` pinskia at gcc dot gnu.org
2024-04-02 21:01 ` pinskia at gcc dot gnu.org
2007-05-02  2:20 [Bug c/31782] New: " truedfx at gentoo dot org
2007-05-02  2:33 ` [Bug target/31782] " pinskia at gcc dot gnu dot org
2007-05-02  4:58 ` truedfx at gentoo dot org
2007-05-02 11:58 ` joseph at codesourcery dot com

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-31782-4-pIsVed1baD@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).