public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bero@arklinux.org To: gcc-gnats@gcc.gnu.org Subject: c/9959: __asm__ no longer accepts linebreaks Date: Wed, 05 Mar 2003 02:56:00 -0000 [thread overview] Message-ID: <20030305025342.20383.qmail@sources.redhat.com> (raw) >Number: 9959 >Category: c >Synopsis: __asm__ no longer accepts linebreaks >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Mar 05 02:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Bernhard Rosenkraenzer >Release: gcc-3_3-branch as of 2003/03/05 >Organization: >Environment: Ark Linux Dockyard (Linux 2.4.21pre5, glibc 2.3.2) >Description: The following code used to work with older gcc versions, doesn't work with almost-3.3 anymore: static unsigned char test[1024]; int main(int argc, char **argv) { __asm__ __volatile__ (" call test"); } Changing it into either static unsigned char test[1024]; int main(int argc, char **argv) { __asm__ __volatile__ (" \ call test"); } or static unsigned char test[1024]; int main(int argc, char **argv) { __asm__ __volatile__ ("call test"); } Works. Intentional change, or bug? >How-To-Repeat: Try to compile the code above. Results with gcc 3.3: test.c:4:31: missing terminating " character test.c: In function `main': test.c:5: error: syntax error before "call" test.c:5:34: missing terminating " character >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-05 2:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-05 2:56 bero [this message] 2003-03-05 7:14 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=20030305025342.20383.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).