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] New: Bogus gimplification of jit code using ptrs to functions Date: Tue, 30 Jun 2015 01:40:00 -0000 [thread overview] Message-ID: <bug-66700-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66700 Bug ID: 66700 Summary: Bogus gimplification of jit code using ptrs to functions Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Blocks: 66627 Target Milestone: --- https://gcc.gnu.org/ml/jit/2015-q2/msg00131.html noted a problem where a ptr to a local was being passed as an argument in a function call built using libgccjit, where the function was a prebuilt one that writes back through the ptr to the local, but where the local wasn't changing. The issue seems to be that during gimplification, the argument changes from &local to: &local.0 and then "local" gets used later on in the caller, not "local.0". Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66627 [Bug 66627] Tracker bug for jit bugs affecting ravi
next reply other threads:[~2015-06-30 1:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 1:40 dmalcolm at gcc dot gnu.org [this message] 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 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@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).