public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/95306] Getting __builtin_sadd_overflow gives the error "unimplemented primitive type for builtin: 42" Date: Wed, 03 Jun 2020 15:15:29 +0000 [thread overview] Message-ID: <bug-95306-4-47O5olag31@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95306-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95306 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:6d36cc21b69d952967a4df6653954f572a101796 commit r11-877-g6d36cc21b69d952967a4df6653954f572a101796 Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Jun 3 08:59:23 2020 -0400 jit: implement BT_CONST_VOLATILE_PTR [PR 95306] gcc/jit/ChangeLog: PR jit/95306 * jit-builtins.c (builtins_manager::make_primitive_type): Implement BT_CONST_VOLATILE_PTR. gcc/testsuite/ChangeLog: PR jit/95306 * jit.dg/test-pr95306-builtin-types.c (create_code): Add test of getting __atomic_load.
next prev parent reply other threads:[~2020-06-03 15:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-24 15:21 [Bug jit/95306] New: Getting __builtin_saddl_overflow " bouanto at zoho dot com 2020-05-26 0:13 ` [Bug jit/95306] Getting __builtin_sadd_overflow " bouanto at zoho dot com 2020-05-26 22:07 ` cvs-commit at gcc dot gnu.org 2020-05-26 22:27 ` dmalcolm at gcc dot gnu.org 2020-06-03 11:46 ` bouanto at zoho dot com 2020-06-03 15:15 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-03 15:18 ` 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-95306-4-47O5olag31@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).