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 tree-optimization/98474] [8/9/10/11 Regression] incorrect results using __uint128_t Date: Tue, 29 Dec 2020 22:27:28 +0000 [thread overview] Message-ID: <bug-98474-4-TkB5KE2uKN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98474 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-12-29 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED
next prev parent reply other threads:[~2020-12-29 22:27 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-29 21:57 [Bug c++/98474] New: " jeffhurchalla at gmail dot com 2020-12-29 22:17 ` [Bug c++/98474] " jeffhurchalla at gmail dot com 2020-12-29 22:27 ` [Bug tree-optimization/98474] [8/9/10/11 Regression] " jakub at gcc dot gnu.org 2020-12-29 22:27 ` jakub at gcc dot gnu.org [this message] 2020-12-30 10:03 ` jakub at gcc dot gnu.org 2020-12-31 2:59 ` jeffhurchalla at gmail dot com 2020-12-31 10:07 ` cvs-commit at gcc dot gnu.org 2020-12-31 10:11 ` [Bug tree-optimization/98474] [8/9/10 " jakub at gcc dot gnu.org 2021-01-01 2:44 ` jeffhurchalla at gmail dot com 2021-01-05 10:44 ` rguenth at gcc dot gnu.org 2021-01-06 9:40 ` cvs-commit at gcc dot gnu.org 2021-01-06 9:46 ` [Bug tree-optimization/98474] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:49 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:09 ` 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-98474-4-TkB5KE2uKN@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).