public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44777] [4.4/4.5/4.6/4.7 Regression] ICE: SIGSEGV with -fprofile-use in gcc.c-torture/execute/comp-goto-2.c Date: Wed, 04 Jan 2012 14:58:00 -0000 [thread overview] Message-ID: <bug-44777-4-uLjapDy8iG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44777-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44777 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-04 14:57:58 UTC --- Created attachment 26239 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26239 gcc47-pr44777.patch Untested fix.
next prev parent reply other threads:[~2012-01-04 14:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44777-4@http.gcc.gnu.org/bugzilla/> 2011-06-27 14:32 ` [Bug middle-end/44777] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2012-01-04 14:28 ` [Bug middle-end/44777] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org 2012-01-04 14:58 ` jakub at gcc dot gnu.org [this message] 2012-01-04 19:42 ` jakub at gcc dot gnu.org 2012-01-05 19:34 ` hubicka at gcc dot gnu.org 2012-01-05 19:54 ` jakub at gcc dot gnu.org 2012-01-05 20:11 ` [Bug middle-end/44777] [4.4/4.5/4.6 " jakub at gcc dot gnu.org 2012-02-09 17:21 ` jakub at gcc dot gnu.org 2012-02-09 21:35 ` [Bug middle-end/44777] [4.4/4.5 " jakub at gcc dot gnu.org 2012-03-13 16:48 ` [Bug middle-end/44777] [4.4 " jakub 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-44777-4-uLjapDy8iG@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).