public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47228] New: likely improper segfault in generated code Date: Tue, 25 Jan 2011 23:05:00 -0000 [thread overview] Message-ID: <bug-47228-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47228 Summary: likely improper segfault in generated code Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: regehr@cs.utah.edu CC: chenyang@cs.utah.edu Host: i686-pc-linux-gnu Target: i686-pc-linux-gnu Build: i686-pc-linux-gnu regehr@home:~/volatile/bugs/tmp343$ current-gcc -O1 small.c -o small regehr@home:~/volatile/bugs/tmp343$ ./small Segmentation fault regehr@home:~/volatile/bugs/tmp343$ current-gcc -v Using built-in specs. COLLECT_GCC=current-gcc COLLECT_LTO_WRAPPER=/mnt/z/z/compiler-install/gcc-r168608-install/libexec/gcc/i686-pc-linux-gnu/4.6.0/lto-wrapper Target: i686-pc-linux-gnu Configured with: ../configure --with-libelf=/usr/local --enable-lto --prefix=/mnt/z/z/compiler-install/gcc-r168608-install --program-prefix=r168608- --enable-languages=c,c++ Thread model: posix gcc version 4.6.0 20110109 (experimental) (GCC) regehr@home:~/volatile/bugs/tmp343$ cat small.c struct S4 { unsigned f0:24; } __attribute__((__packed__)); struct S4 g_10 = { 6210831 }; struct S4 func_2 (int x) { struct S4 l_8[2] = { {0}, {0} }; g_10 = l_8[1]; for (; x<2; x++) { struct S4 tmp = { 11936567 }; l_8[x] = tmp; } return g_10; } int main (void) { func_2 (0); return 0; }
next reply other threads:[~2011-01-25 23:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-25 23:05 LpSolit at netscape dot net [this message] 2011-01-26 0:17 ` [Bug tree-optimization/47228] [4.6 Regression] wrong code with loop pinskia at gcc dot gnu.org 2011-01-26 9:50 ` jakub at gcc dot gnu.org 2011-01-26 9:50 ` jakub at gcc dot gnu.org 2011-01-26 9:53 ` jakub at gcc dot gnu.org 2011-01-26 19:58 ` jamborm at gcc dot gnu.org 2011-01-26 21:14 ` jamborm at gcc dot gnu.org 2011-01-27 14:10 ` jamborm at gcc dot gnu.org 2011-01-27 14:26 ` jamborm at gcc dot gnu.org 2011-02-02 18:16 ` dnovillo 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-47228-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: 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).