public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libmudflap/40778] [4.5/4.6 Regression] Mudflap instrumentation missing in cloned function.
Date: Thu, 16 Dec 2010 13:07:00 -0000	[thread overview]
Message-ID: <bug-40778-4-9Y1iBcNbQ8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40778-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40778

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.5.2                       |4.5.3

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-12-16 13:02:59 UTC ---
GCC 4.5.2 is being released, adjusting target milestone.


       reply	other threads:[~2010-12-16 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40778-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:07 ` rguenth at gcc dot gnu.org [this message]
2011-04-28 14:59 ` [Bug libmudflap/40778] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-13 20:27 ` steven at gcc dot gnu.org
2012-01-17 11:39 ` jakub at gcc dot gnu.org
2012-01-17 17:02 ` fche at redhat dot com
2012-01-19 19:33 ` jakub at gcc dot gnu.org
2012-01-19 19:43 ` [Bug libmudflap/40778] [4.5/4.6 " jakub at gcc dot gnu.org
2012-02-09 17:25 ` jakub at gcc dot gnu.org
2012-02-09 21:40 ` [Bug libmudflap/40778] [4.5 " jakub at gcc dot gnu.org
2012-02-09 21:49 ` jakub at gcc dot gnu.org
2009-07-16 19:05 [Bug libmudflap/40778] New: " tjruwase at google dot com
2010-07-31  9:35 ` [Bug libmudflap/40778] [4.5/4.6 " rguenth 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=bug-40778-4-9Y1iBcNbQ8@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: link
Be 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).