public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59708] clang-compatible checked arithmetic builtins Date: Wed, 05 Nov 2014 11:59:00 -0000 [thread overview] Message-ID: <bug-59708-4-zypxA0QUq6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59708-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59708 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #33855|0 |1 is obsolete| | --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 33891 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33891&action=edit gcc5-pr59708-wip2.patch Updated patch, this time __builtin_umul{,l,ll}_overflow should work fully, and with the exception of widest type ({,un}signed __int128 on targets that do support that, {,un}signed long long otherwise) also the type-generic variants. What is still unhandled is in the widest type signed +- signed -> unsigned, unsigned +- unsigned -> signed and mixed sign (either between operands, or between operand and result) multiplication in the widest type.
next prev parent reply other threads:[~2014-11-05 11:59 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-07 6:14 [Bug c/59708] New: " josh at joshtriplett dot org 2014-01-07 11:21 ` [Bug c/59708] " rguenth at gcc dot gnu.org 2014-01-07 11:38 ` jakub at gcc dot gnu.org 2014-01-07 11:52 ` rguenth at gcc dot gnu.org 2014-01-07 12:33 ` josh at joshtriplett dot org 2014-01-07 17:15 ` joseph at codesourcery dot com 2014-01-07 20:16 ` josh at joshtriplett dot org 2014-08-24 7:05 ` Martin.vGagern at gmx dot net 2014-08-24 7:47 ` Martin.vGagern at gmx dot net 2014-08-24 18:40 ` manu at gcc dot gnu.org 2014-10-31 17:36 ` jakub at gcc dot gnu.org 2014-11-05 11:59 ` jakub at gcc dot gnu.org [this message] 2014-11-06 17:34 ` jakub at gcc dot gnu.org 2014-11-22 1:29 ` danglin at gcc dot gnu.org 2014-11-22 7:31 ` jakub at gcc dot gnu.org 2014-11-22 13:24 ` dave.anglin at bell dot net 2014-11-24 14:23 ` mpolacek at gcc dot gnu.org 2014-11-24 14:26 ` trippels at gcc dot gnu.org 2014-12-02 23:27 ` schwab@linux-m68k.org 2014-12-03 10:19 ` jakub at gcc dot gnu.org 2014-12-03 20:35 ` jakub at gcc dot gnu.org 2014-12-03 20:39 ` jakub at gcc dot gnu.org 2014-12-03 20:40 ` jakub at gcc dot gnu.org 2014-12-17 22:52 ` pthaugen at gcc dot gnu.org 2015-01-05 17:05 ` pthaugen 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-59708-4-zypxA0QUq6@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).