public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asharif at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/51975] ICE in gcc in convert_move, at expr.c:326 with fprofile-use when source changes from fprofile-generate Date: Tue, 24 Jan 2012 22:30:00 -0000 [thread overview] Message-ID: <bug-51975-4-qlI1uoR24k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51975-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51975 asharif at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #26445|0 |1 is obsolete| | --- Comment #3 from asharif at gcc dot gnu.org 2012-01-24 20:10:21 UTC --- Created attachment 26446 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26446 Proposed fix.
next prev parent reply other threads:[~2012-01-24 20:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 1:16 [Bug gcov-profile/51975] New: " asharif at gcc dot gnu.org 2012-01-24 1:28 ` [Bug gcov-profile/51975] " asharif at gcc dot gnu.org 2012-01-24 22:24 ` asharif at gcc dot gnu.org 2012-01-24 22:30 ` asharif at gcc dot gnu.org [this message] 2012-07-22 0:11 ` steven 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-51975-4-qlI1uoR24k@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).