public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "webmaster at openhardware dot de" <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: Thu, 29 Mar 2012 13:42:00 -0000 [thread overview] Message-ID: <bug-52554-4-XgKhLP9Mjs@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 --- Comment #7 from openhardware <webmaster at openhardware dot de> 2012-03-29 13:40:14 UTC --- "Alternatively, change the documentation to the effect that invalid assembly code and valid (but semantically wrong) assembly code aren't necessarily compiler bugs." Its a "windows-approach" Not a bug but a feature. Intel calls their errata sheets for silicon bugs "specification update" That's really sweet, so whats a spec for? Please fix it in gcc to be a syntax error, or at least throw a warning like "Illegal variable name found in line # might cause illegal assembly code and thus unpredictable results!". This would be the best, so if one has a special "geeks-assembler", that allows a $ to be send to the assembler, so one could use it, for what special geeks-reason ever (may be, to have a hack to illegally allign a variable in memory between the rails of the processors word length in order to smear it into two registers [highbyte of lower register and lowbyte of upper register] of some IO or to do some other dirty stuff directly from hell)
next prev parent reply other threads:[~2012-03-29 13:41 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 ` [Bug target/52554] " fw at gcc dot gnu.org 2012-03-28 9:45 ` 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 [this message] 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-XgKhLP9Mjs@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).