public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64078] FAIL: c-c++-common/ubsan/object-size-9.c
Date: Sat, 11 Apr 2015 20:38:00 -0000 [thread overview]
Message-ID: <bug-64078-4-ohb95eO1Tw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64078-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64078
--- Comment #11 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
I don't know if that is a bug or not.
I see that -fpic does not inline f2 and f3.
The two messages seem to be always missing when
not inlined...
So, how about this:
Index: gcc/testsuite/c-c++-common/ubsan/object-size-9.c
===================================================================
--- gcc/testsuite/c-c++-common/ubsan/object-size-9.c (revision 222007)
+++ gcc/testsuite/c-c++-common/ubsan/object-size-9.c (working copy)
@@ -11,7 +11,7 @@
#endif
struct U { int a : 5; int b : 19; int c : 8; };
struct S { struct U d[10]; };
-struct S s;
+struct S s __attribute__((aligned(4096)));
int
f1 (struct T x, int i)
@@ -27,7 +27,7 @@
/* { dg-output "\[^\n\r]*\\^\[^\n\r]*(\n|\r\n|\r)" } */
#ifdef __cplusplus
-struct C
+inline struct C
f2 (int i)
{
struct C x;
@@ -41,7 +41,7 @@
/* { dg-output "\[^\n\r]*\[^\n\r]*(\n|\r\n|\r)" { target { c++ } } } */
/* { dg-output "\[^\n\r]*\\^\[^\n\r]*(\n|\r\n|\r)" { target { c++ } } } */
-struct C
+inline struct C
f3 (int i)
{
struct C x;
With this patch,
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c
--target_board='unix{-fpic,-mcmodel=medium,-fpic\
-mcmodel=medium,-mcmodel=large,-fpic\ -mcmodel=large}'"
passes, but
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c
--target_board='unix{-fno-inline}'"
still fails of course.
next prev parent reply other threads:[~2015-04-11 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64078-4@http.gcc.gnu.org/bugzilla/>
2014-11-26 12:47 ` hjl.tools at gmail dot com
2015-01-12 23:10 ` bernd.edlinger at hotmail dot de
2015-01-12 23:51 ` hjl.tools at gmail dot com
2015-04-02 11:36 ` vries at gcc dot gnu.org
2015-04-02 15:57 ` vries at gcc dot gnu.org
2015-04-11 17:45 ` bernd.edlinger at hotmail dot de
2015-04-11 19:24 ` bernd.edlinger at hotmail dot de
2015-04-11 19:37 ` bernd.edlinger at hotmail dot de
2015-04-11 20:38 ` bernd.edlinger at hotmail dot de [this message]
2015-04-12 7:14 ` bernd.edlinger at hotmail dot de
2015-06-10 23:43 ` bernd.edlinger at hotmail dot de
2015-09-17 19:43 ` edlinger at gcc dot gnu.org
2015-09-17 19:45 ` edlinger 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-64078-4-ohb95eO1Tw@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).