public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/20567] New: dg-options in gcc.c-torture Date: Sun, 20 Mar 2005 13:26:00 -0000 [thread overview] Message-ID: <20050320132624.20567.jsm28@gcc.gnu.org> (raw) Some tests in gcc.c-torture use dg-options inappropriately. gcc.c-torture/execute ignores dg-options settings, but pr7284-1.c and wchar_t-1.c use them. I think the proper fix would be to make that directory honour dg-options. If it is made to use the dg harness it might also be possible to get rid of most of the .x files in c-torture by moving them into test annotations within the testcase files. In gcc.c-torture/compile, tests 20031125-1.c, 20031125-2.c, 20031203-1.c and acc1.c specify -O2. As the point of the torture tests is to iterate over different optimization options, tests should not specify any options like -O2 which are included in that iteration; only other special options (such as -ffast-math for acc1.c). compile/981006-1.c looks like a diagnostic test and as such (a) should not use -w, (b) should better be in gcc.dg/torture/. -- Summary: dg-options in gcc.c-torture Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jsm28 at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,janis187 at us dot ibm dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567
next reply other threads:[~2005-03-20 13:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-20 13:26 jsm28 at gcc dot gnu dot org [this message] 2005-03-20 17:48 ` [Bug testsuite/20567] " pinskia at gcc dot gnu dot org 2005-06-05 11:32 ` jsm28 at gcc dot gnu dot 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=20050320132624.20567.jsm28@gcc.gnu.org \ --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).