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 middle-end/46287] No thunk info on call graph edges leads to miscompilations
Date: Mon, 22 Nov 2010 21:48:00 -0000	[thread overview]
Message-ID: <bug-46287-4-fDjMv0v8g3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46287-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> 2010-11-22 21:47:19 UTC ---
Patch pinged: http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02291.html


  parent reply	other threads:[~2010-11-22 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 12:57 [Bug middle-end/46287] New: " jamborm at gcc dot gnu.org
2010-11-03 12:57 ` [Bug middle-end/46287] " jamborm at gcc dot gnu.org
2010-11-11 11:03 ` jamborm at gcc dot gnu.org
2010-11-22 21:48 ` jamborm at gcc dot gnu.org [this message]
2010-12-15 13:20 ` jamborm at gcc dot gnu.org
2010-12-15 14:32 ` jamborm 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-46287-4-fDjMv0v8g3@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).