public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/57358] segmentation fault with attribute(optimize(O0)) Date: Mon, 24 Jun 2013 12:59:00 -0000 [thread overview] Message-ID: <bug-57358-4-2anXxFOd3I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57358-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57358 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> --- Author: jamborm Date: Mon Jun 24 12:57:52 2013 New Revision: 200370 URL: http://gcc.gnu.org/viewcvs?rev=200370&root=gcc&view=rev Log: 2013-06-24 Martin Jambor <mjambor@suse.cz> PR tree-optimization/57358 * ipa-prop.c (parm_ref_data_preserved_p): Always return true when not optimizing. testsuite/ * gcc.dg/ipa/pr57358.c: New test. Added: branches/gcc-4_8-branch/gcc/testsuite/gcc.dg/ipa/pr57358.c Modified: branches/gcc-4_8-branch/gcc/ChangeLog branches/gcc-4_8-branch/gcc/ipa-prop.c branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2013-06-24 12:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-21 15:17 [Bug tree-optimization/57358] New: " nbkolchin at gmail dot com 2013-06-04 14:16 ` [Bug tree-optimization/57358] " nbkolchin at gmail dot com 2013-06-04 15:14 ` nbkolchin at gmail dot com 2013-06-11 12:00 ` jamborm at gcc dot gnu.org 2013-06-14 10:00 ` jamborm at gcc dot gnu.org 2013-06-24 12:52 ` jamborm at gcc dot gnu.org 2013-06-24 12:59 ` jamborm at gcc dot gnu.org [this message]
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-57358-4-2anXxFOd3I@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).