public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/40704] New: ^M? in testsuite log leads to binary attachment Date: Thu, 09 Jul 2009 20:51:00 -0000 [thread overview] Message-ID: <bug-40704-682@http.gcc.gnu.org/bugzilla/> (raw) Some gcc test results contain binary attachment: http://gcc.gnu.org/ml/gcc-testresults/2009-07/msg00830.html The problem is "^M?" in === libffi tests === Running target unix/-m32 XPASS: libffi.call/cls_dbls_struct.c -O0 -W -Wall output pattern test, 1.0 2.0^M? XPASS: libffi.call/cls_dbls_struct.c -O2 output pattern test, 1.0 2.0^M? XPASS: libffi.call/cls_dbls_struct.c -O3 output pattern test, 1.0 2.0^M? XPASS: libffi.call/cls_dbls_struct.c -Os output pattern test, 1.0 2.0^M? XPASS: libffi.call/cls_dbls_struct.c -O2 -fomit-frame-pointer output pattern test, 1.0 2.0^M? === libffi Summary for unix/-m32 === They come from /* { dg-output "1.0 2.0\n" { xfail x86_64-*-linux-* } } */ in libffi.call/cls_dbls_struct.c. -- Summary: ^M? in testsuite log leads to binary attachment Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40704
next reply other threads:[~2009-07-09 20:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-09 20:51 hjl dot tools at gmail dot com [this message] 2009-07-13 1:19 ` [Bug testsuite/40704] " bje at gcc dot gnu dot org 2009-07-28 18:12 ` hjl dot tools at gmail dot com 2009-07-28 20:02 ` ubizjak at gmail dot com 2009-08-05 18:47 ` hjl dot tools at gmail dot com 2009-08-18 19:41 ` hjl at gcc dot gnu dot org 2009-09-28 15:48 ` hjl dot tools at gmail dot com
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-40704-682@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).