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/35843] New: gcc.dg/pr30957-1.c and gcc.dg/var-expand1.c don't work Date: Sun, 06 Apr 2008 15:13:00 -0000 [thread overview] Message-ID: <bug-35843-682@http.gcc.gnu.org/bugzilla/> (raw) From http://gcc.gnu.org/ml/gcc-testresults/2008-04/msg00420.html ERROR: gcc.dg/pr30957-1.c: no files matched glob pattern "hard_float9950.c.[0-9][0-9][0-9]r.expand" for " dg-require-effective-target 8 hard_float " UNRESOLVED: gcc.dg/pr30957-1.c: no files matched glob pattern "hard_float9950.c.[0-9][0-9][0-9]r.expand" for " dg-require-effective-target 8 hard_float " ERROR: gcc.dg/var-expand1.c: can't read "et_cache(hard_float,value)": no such element in array for " dg-require-effective-target 4 hard_float " UNRESOLVED: gcc.dg/var-expand1.c: can't read "et_cache(hard_float,value)": no such element in array for " dg-require-effective-target 4 hard_float " On Linux/Intel64, I got Executing on host: /export/build/gnu/gcc/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/gcc/build-x86_64-linux/gcc/ hard_float1773.c -fdump-rtl-expand -fno-show-column -S -m32 -o hard_float1773.s (timeout = 300) cc1: error: unrecognized command line option "-fdump-rtl-expand"^M compiler exited with status 1 Executing on host: /export/build/gnu/gcc/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/gcc/build-x86_64-linux/gcc/ /export/gnu/src/gcc/gcc/gcc/testsuite/gcc.dg/va-arg-pack-len-2.c -O2 -fno-show-column -S -m32 -o va-arg-pack-len-2.s (timeout = 300) In function 'myopen',^M inlined from 'main' at /export/gnu/src/gcc/gcc/gcc/testsuite/gcc.dg/va-arg-pack-len-2.c:39:^M /export/gnu/src/gcc/gcc/gcc/testsuite/gcc.dg/va-arg-pack-len-2.c:24: error: call to 'error_open_missing_mode' declared with attribute error: open with O_CREAT needs 3 arguments, only 2 were given^M In function 'myopen',^M inlined from 'main' at /export/gnu/src/gcc/gcc/gcc/testsuite/gcc.dg/va-arg-pack-len-2.c:40:^M /export/gnu/src/gcc/gcc/gcc/testsuite/gcc.dg/va-arg-pack-len-2.c:18: warning: call to 'warn_open_too_many_arguments' declared with attribute warning: open called with more than 3 arguments^M compiler exited with status 1 -- Summary: gcc.dg/pr30957-1.c and gcc.dg/var-expand1.c don't work Product: gcc Version: 4.4.0 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=35843
next reply other threads:[~2008-04-06 15:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-06 15:13 hjl dot tools at gmail dot com [this message] 2008-04-06 15:17 ` [Bug testsuite/35843] [4.4 Regression]: " hjl dot tools at gmail dot com 2008-04-07 1:14 ` [Bug middle-end/35843] " pinskia at gcc dot gnu dot org 2008-04-09 18:11 ` pinskia at gcc dot gnu dot org 2008-04-11 10:17 ` [Bug testsuite/35843] [4.4 Regression]: -fdump-rtl-expand does not exist anymore ubizjak at gmail dot com 2008-04-11 11:44 ` ubizjak at gmail dot com 2008-04-11 16:10 ` pinskia at gcc dot gnu dot org 2008-04-16 13:03 ` hjl dot tools at gmail dot com 2008-04-20 20:45 ` rguenth at gcc dot gnu dot org 2008-04-25 23:15 ` hubicka at gcc dot gnu dot org 2008-04-26 9:57 ` ubizjak 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-35843-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).