public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97950] Unoptimal code generation with __builtin_*_overflow{,_p} for short and __int128 Date: Mon, 23 Nov 2020 18:25:14 +0000 [thread overview] Message-ID: <bug-97950-4-bmxYjG2bb7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97950-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97950 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement
next prev parent reply other threads:[~2020-11-23 18:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-23 13:49 [Bug tree-optimization/97950] New: " denis.campredon at gmail dot com 2020-11-23 16:35 ` [Bug tree-optimization/97950] " jakub at gcc dot gnu.org 2020-11-23 18:01 ` denis.campredon at gmail dot com 2020-11-23 18:25 ` pinskia at gcc dot gnu.org [this message] 2020-11-23 20:26 ` [Bug target/97950] " ubizjak at gmail dot com 2020-11-23 20:36 ` jakub at gcc dot gnu.org 2020-11-24 9:46 ` cvs-commit at gcc dot gnu.org 2020-11-24 9:51 ` [Bug target/97950] Unoptimal code generation with __builtin_*_overflow{,_p} for short jakub 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-97950-4-bmxYjG2bb7@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).