public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "epperly2 at llnl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32182] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault Date: Fri, 01 Jun 2007 20:53:00 -0000 [thread overview] Message-ID: <20070601205313.5045.qmail@sourceware.org> (raw) In-Reply-To: <bug-32182-10468@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from epperly2 at llnl dot gov 2007-06-01 20:53 ------- To avoid depending on system #include files, the example has typedef unsigned int size_t; hardwired in the code. This may be an incorrect definition for some platforms. Oddly enough, if I delete NextClass and make TestClass inherit directly from BaseClass, the program no longer segfaults. I am not sure if all the features of this example are strictly necessary. I basically created a new program from scratch that has the same characteristics as the original 100+K program, and I added things until it reproduced the same behavior. -- epperly2 at llnl dot gov changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|-fstrict-aliasing |-fstrict-aliasing |optimizations cause |optimizations cause |constructor not to run in |constructor not to run for |causing segfault |object causing segfault http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32182
next prev parent reply other threads:[~2007-06-01 20:53 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-01 20:41 [Bug c++/32182] New: -fstrict-aliasing optimizations cause constructor not to run in " epperly2 at llnl dot gov 2007-06-01 20:44 ` [Bug c++/32182] " epperly2 at llnl dot gov 2007-06-01 20:53 ` epperly2 at llnl dot gov [this message] 2007-06-01 21:07 ` [Bug c++/32182] -fstrict-aliasing optimizations cause constructor not to run for object " epperly2 at llnl dot gov 2007-06-01 21:16 ` pinskia at gcc dot gnu dot org 2007-06-01 21:24 ` epperly2 at llnl dot gov 2007-06-01 22:04 ` epperly2 at llnl dot gov 2007-06-01 22:12 ` epperly2 at llnl dot gov 2007-06-01 22:14 ` epperly2 at llnl dot gov 2007-06-01 23:25 ` epperly2 at llnl dot gov 2007-06-01 23:57 ` pinskia at gcc dot gnu dot org 2007-06-02 2:52 ` epperly2 at llnl dot gov 2007-06-02 11:35 ` [Bug c++/32182] [4.2 Regression] " rguenth at gcc dot gnu dot org 2007-06-02 11:45 ` rguenth at gcc dot gnu dot org 2007-06-04 12:58 ` rguenth at gcc dot gnu dot org 2007-07-04 3:23 ` mmitchel at gcc dot gnu dot org 2007-07-20 3:47 ` mmitchel at gcc dot gnu dot org 2007-10-04 1:30 ` jason at gcc dot gnu dot org 2007-10-09 19:22 ` mmitchel at gcc dot gnu dot org 2008-02-01 16:57 ` jsm28 at gcc dot gnu dot org 2008-05-19 20:27 ` jsm28 at gcc dot gnu dot org 2009-03-30 21:50 ` 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=20070601205313.5045.qmail@sourceware.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).