public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bero@arklinux.org To: gcc-gnats@gcc.gnu.org Subject: inline-asm/10870: Problems with # as comment character in asm code Date: Mon, 19 May 2003 18:16:00 -0000 [thread overview] Message-ID: <20030519180604.13486.qmail@sources.redhat.com> (raw) >Number: 10870 >Category: inline-asm >Synopsis: Problems with # as comment character in asm code >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon May 19 18:16:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: bero@arklinux.org >Release: 3.3 >Organization: >Environment: Ark Linux 1.0 alpha 8 >Description: Using gcc foo.S, with foo.S being an assembler file, works, unless the assembler file includes comments in the style # foo with # being the first character in the line (gcc mistakes it as preprocessor directive). Not 100% sure if this is a bug or an intentional feature removal; used to work in older releases. >How-To-Repeat: Compile e.g. syslinux 2.04 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-05-19 18:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 18:16 bero [this message] 2003-05-19 20:12 neil
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=20030519180604.13486.qmail@sources.redhat.com \ --to=bero@arklinux.org \ --cc=gcc-gnats@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).