public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com To: gcc-gnats@gcc.gnu.org Subject: target/3023: Failure of test gcc.dg/asm-fs-1.c on cygwin Date: Thu, 31 May 2001 22:26:00 -0000 [thread overview] Message-ID: <20010601051733.1919.qmail@sourceware.cygnus.com> (raw) >Number: 3023 >Category: target >Synopsis: Failure of test gcc.dg/asm-fs-1.c on cygwin >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 31 22:26:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: David Billinghurst >Release: unknown-1.0 >Organization: >Environment: i686-pc-cygwin >Description: The failure of test gcc.dg/asm-fs-1.c on cygwin is a regression from gcc-2.95. FAIL: gcc.dg/asm-fs-1.c scan-assembler-not \*_bar The assembler output .file "asm-fs-1.c" ..section .text$*_bar,"x" .align 16 ..globl _bar .def _bar; .scl 2; .type 32; .endef _bar: pushl %ebp movl %esp, %ebp popl %ebp ret ..globl _baz ..section .data$*_baz,"w" .align 4 _baz: .long 3 With gcc version 2.95.3-4 (cygwin special) I get .file "asm-fs-1.c" gcc2_compiled.: .file "asm-fs-1.c" gcc2_compiled.: ___gnu_compiled_c: .text .align 4 .globl _bar .def _bar; .scl 2; .type 32; .endef _bar: pushl %ebp movl %esp,%ebp L2: movl %ebp,%esp popl %ebp ret .globl _baz .data .align 4 _baz: .long 3 Alexandre Oliva said: It tests that the `*' doesn't make it to the output ssembly. Since it does, the test fails, indicating a bug in the Cygwin output macros. > .section .text$*_bar,"x" ^ > .section .data$*_baz,"w" ^ >How-To-Repeat: gcc -S gcc/testsuite/gcc.dg/asm-fs-1.c examine asm-fs-1.s >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-05-31 22:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-31 22:26 David.Billinghurst [this message] 2001-08-23 17:26 target/3023 " Billinghurst, David (CRTS) 2001-11-10 7:26 target/3023: " billingd 2001-11-10 10:46 billingd
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=20010601051733.1919.qmail@sourceware.cygnus.com \ --to=david.billinghurst@riotinto.com \ --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).