public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/52665] scan-assembler output produces wrong FAIL due to matching .ident Date: Tue, 27 Mar 2012 18:03:00 -0000 [thread overview] Message-ID: <bug-52665-4-gZirCIVsJC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52665-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52665 --- Comment #2 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2012-03-27 18:01:13 UTC --- Author: mrs Date: Tue Mar 27 18:01:06 2012 New Revision: 185889 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=185889 Log: PR target/52665 * gcc.target/i386/pr28946.c: Use -fno-ident to avoid spurious failures that match branch names. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.target/i386/pr28946.c
next prev parent reply other threads:[~2012-03-27 18:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-22 12:02 [Bug testsuite/52665] New: " aldot at gcc dot gnu.org 2012-03-22 12:11 ` [Bug testsuite/52665] " aldot at gcc dot gnu.org 2012-03-27 7:04 ` aldot at gcc dot gnu.org 2012-03-27 18:03 ` mrs at gcc dot gnu.org [this message] 2012-03-27 18:09 ` mrs 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-52665-4-gZirCIVsJC@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).