public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55030] New: [4.8 Regression]: gcc.c-torture/execute/builtins/memcpy-chk.c execution, -Os (et al)
Date: Tue, 23 Oct 2012 00:58:00 -0000 [thread overview]
Message-ID: <bug-55030-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55030
Bug #: 55030
Summary: [4.8 Regression]:
gcc.c-torture/execute/builtins/memcpy-chk.c execution,
-Os (et al)
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
Target: i686-pc-linux-gnu
As noted in <http://gcc.gnu.org/ml/gcc-patches/2012-10/msg01968.html>, revision
r192676 introduced the following test-suite regressions for i686-pc-linux-gnu
or x86_64-pc-linux-gnu with -m32:
Running
/home/hp/gcctop/tmp/base/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
...
FAIL: gcc.c-torture/execute/builtins/memcpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/memmove-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/mempcpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/memset-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/snprintf-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/sprintf-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/stpcpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/stpncpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/strcat-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/strcpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/strncat-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/strncpy-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/vsnprintf-chk.c execution, -Os
FAIL: gcc.c-torture/execute/builtins/vsprintf-chk.c execution, -Os
next reply other threads:[~2012-10-23 0:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 0:58 hp at gcc dot gnu.org [this message]
2012-10-23 1:05 ` [Bug middle-end/55030] " hp at gcc dot gnu.org
2012-10-23 1:08 ` hp at gcc dot gnu.org
2012-10-23 1:09 ` hp at gcc dot gnu.org
2012-10-23 9:39 ` rguenth at gcc dot gnu.org
2012-11-12 4:37 ` hp at gcc dot gnu.org
2012-11-12 4:54 ` hp at gcc dot gnu.org
2012-11-26 3:22 ` hp at gcc dot gnu.org
2012-11-26 3:26 ` hp at gcc dot gnu.org
2012-11-27 7:41 ` krebbel at gcc dot gnu.org
2012-11-27 11:55 ` hp at gcc dot gnu.org
2012-11-27 23:16 ` hp at gcc dot gnu.org
2013-02-16 9:37 ` ebotcazou at gcc dot gnu.org
2013-02-16 9:44 ` ebotcazou at gcc dot gnu.org
2013-02-17 0:33 ` hp at gcc dot gnu.org
2013-02-18 10:48 ` ebotcazou at gcc dot gnu.org
2013-02-18 22:21 ` hp at gcc dot gnu.org
2013-02-19 11:32 ` ebotcazou at gcc dot gnu.org
2013-06-03 8:37 ` mikpe at it dot uu.se
2013-06-03 22:32 ` hp at gcc dot gnu.org
2013-06-08 7:50 ` ebotcazou at gcc dot gnu.org
2013-07-03 14:44 ` hp 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-55030-4@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: link
Be 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).