public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbeulich at suse dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53929] [meta-bug] -masm=intel with global symbol Date: Thu, 10 Jun 2021 07:25:03 +0000 [thread overview] Message-ID: <bug-53929-4-lGrVnNXI9w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53929-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929 --- Comment #11 from jbeulich at suse dot com --- I have a rough plan on the gas side, but that will then need a gcc side change as well: For a couple of years we have had quoted symbol names there. While this doesn't currently work right in a number of cases (including the one needed here) the plan is to make e.g. mov eax, "ecx" not be treated the same as mov eax, ecx but considering "ecx" a symbol name due to the quotation. Obviously gcc's configure mechanism would then need to detect the assemblers capability of understanding this, and quote symbol names accordingly (perhaps universally rather than special-casing any particular names). While this isn't MASM-compatible (MASM treats "ecx" in such a case as an immediate), I view this as less of a problem than using e.g. Arm's model of enclosing a register name in parentheses to designate it as a symbol name: mov eax, (ecx) MASM treats this the same as with no parentheses present, and I consider this form to be more likely to be used in code ported from MASM than double quoted literals used as immediate constants. (Regardless of the choice in the end it may turn out necessary to hide the new behavior behind a new command line option and/or directive extension.)
next prev parent reply other threads:[~2021-06-10 7:25 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-11 15:39 [Bug c/53929] New: Bug in the use of Intel asm syntax when a global is named "and" louis.granboulan.developer at gmail dot com 2020-09-05 7:49 ` [Bug target/53929] " u1049321969 at caramail dot com 2020-09-06 18:42 ` asolokha at gmx dot com 2020-09-07 10:21 ` jakub at gcc dot gnu.org 2020-09-07 10:45 ` u1049321969 at caramail dot com 2020-09-07 10:54 ` jakub at gcc dot gnu.org 2020-10-26 10:17 ` jbeulich at suse dot com 2020-10-26 10:23 ` jbeulich at suse dot com 2020-12-31 15:06 ` [Bug target/53929] [meta-bug] -masm=intel with global symbol hjl.tools at gmail dot com 2020-12-31 15:07 ` hjl.tools at gmail dot com 2020-12-31 15:08 ` hjl.tools at gmail dot com 2020-12-31 15:08 ` hjl.tools at gmail dot com 2021-06-10 7:25 ` jbeulich at suse dot com [this message] 2023-05-04 4:20 ` pinskia at gcc dot gnu.org 2023-05-04 4:37 ` lh_mouse at 126 dot com 2023-05-04 6:21 ` jbeulich at suse dot com 2023-05-04 7:02 ` lh_mouse at 126 dot com 2023-05-04 7:15 ` jbeulich at suse dot com 2023-05-04 7:24 ` lh_mouse at 126 dot com 2023-05-04 13:14 ` lh_mouse at 126 dot com 2023-05-11 10:58 ` lh_mouse at 126 dot com 2023-05-11 11:35 ` jbeulich at suse dot com 2023-05-11 12:19 ` lh_mouse at 126 dot com 2023-05-11 14:30 ` jbeulich at suse dot com 2023-05-11 14:48 ` lh_mouse at 126 dot com 2024-01-18 5:38 ` lh_mouse at 126 dot com 2024-01-23 1:11 ` lh_mouse at 126 dot com 2024-01-24 2:16 ` lh_mouse at 126 dot com 2024-01-31 20:07 ` egallager 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-53929-4-lGrVnNXI9w@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: linkBe 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).