public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64807] [5 Regression] Wrong-code because of wide-int division
Date: Tue, 27 Jan 2015 00:29:00 -0000 [thread overview]
Message-ID: <bug-64807-4-jr9gzGpSNr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64807-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64807
Kenneth Zadeck <zadeck at naturalbridge dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zadeck at naturalbridge dot com
--- Comment #2 from Kenneth Zadeck <zadeck at naturalbridge dot com> ---
(In reply to Jakub Jelinek from comment #1)
> Created attachment 34582 [details]
> gcc5-pr64807.patch
>
> Untested fix.
This looks ok to me.
next prev parent reply other threads:[~2015-01-27 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 18:31 [Bug tree-optimization/64807] New: " jakub at gcc dot gnu.org
2015-01-26 18:34 ` [Bug tree-optimization/64807] " jakub at gcc dot gnu.org
2015-01-27 0:29 ` zadeck at naturalbridge dot com [this message]
2015-01-27 8:27 ` jakub at gcc dot gnu.org
2015-01-27 8:48 ` jakub at gcc dot gnu.org
2015-01-28 18:26 ` LpSolit at netscape dot net
2015-02-03 9:40 ` jakub at gcc dot gnu.org
2015-03-09 20:49 ` trippels 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-64807-4-jr9gzGpSNr@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: link
Be 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).