public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/66700] Bogus gimplification of jit code using ptrs to functions Date: Tue, 30 Jun 2015 01:50:00 -0000 [thread overview] Message-ID: <bug-66700-4-QeKc3gIRp9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66700-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66700 --- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Created attachment 35876 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35876&action=edit Dump of initial GENERIC form of function
next prev parent reply other threads:[~2015-06-30 1:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 1:40 [Bug jit/66700] New: " dmalcolm at gcc dot gnu.org 2015-06-30 1:43 ` [Bug jit/66700] " dmalcolm at gcc dot gnu.org 2015-06-30 1:50 ` dmalcolm at gcc dot gnu.org [this message] 2015-06-30 2:13 ` dmalcolm at gcc dot gnu.org 2015-06-30 2:16 ` dmalcolm at gcc dot gnu.org 2015-07-01 12:51 ` dmalcolm at gcc dot gnu.org 2015-07-01 14:49 ` dmalcolm at gcc dot gnu.org 2015-07-01 15:10 ` dmalcolm 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-66700-4-QeKc3gIRp9@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).