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/66812] New: jit code-generation example that required -fno-strict-aliasing to work Date: Wed, 08 Jul 2015 14:27:00 -0000 [thread overview] Message-ID: <bug-66812-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66812 Bug ID: 66812 Summary: jit code-generation example that required -fno-strict-aliasing to work 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: --- A user reported a problem on the jit mailing list where incorrect code was generated by libgccjit at the equivalent -O2 and above unless -fno-strict-aliasing was supplied: https://gcc.gnu.org/ml/jit/2015-q3/msg00015.html 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-07-08 14:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-08 14:27 dmalcolm at gcc dot gnu.org [this message] 2015-07-09 19:09 ` [Bug jit/66812] jit code-generation example that unexpectedly " dmalcolm at gcc dot gnu.org 2015-07-09 19:11 ` dmalcolm at gcc dot gnu.org 2015-07-09 19:13 ` dmalcolm at gcc dot gnu.org 2015-07-09 19:16 ` dmalcolm at gcc dot gnu.org 2015-07-09 19:19 ` dmalcolm at gcc dot gnu.org 2015-07-09 20:43 ` pinskia at gcc dot gnu.org 2015-07-09 21:02 ` dmalcolm at gcc dot gnu.org 2015-07-09 21:03 ` dmalcolm at gcc dot gnu.org 2015-07-09 21:04 ` dmalcolm at gcc dot gnu.org 2015-07-09 21:35 ` 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-66812-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).