public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jogo at openwrt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54295] [4.7 Regression] Widening multiply-accumulate operation uses wrong value extension
Date: Mon, 29 Apr 2013 12:56:00 -0000 [thread overview]
Message-ID: <bug-54295-4-TIPFSjTkJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54295-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54295
Jonas Gorski <jogo at openwrt dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jogo at openwrt dot org
--- Comment #9 from Jonas Gorski <jogo at openwrt dot org> 2013-04-29 12:56:23 UTC ---
I want to confirm that this is still an issue in 4.7.3, also applies to at
least mips32 (did not test mips64) and causes miscompilations in the linux
kernel there.
next prev parent reply other threads:[~2013-04-29 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 12:46 [Bug tree-optimization/54295] New: [4.7 regression] " rearnsha at gcc dot gnu.org
2012-08-17 12:47 ` [Bug tree-optimization/54295] " rearnsha at gcc dot gnu.org
2012-08-17 12:50 ` rearnsha at gcc dot gnu.org
2012-08-17 13:13 ` [Bug tree-optimization/54295] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-08-20 12:50 ` rearnsha at gcc dot gnu.org
2012-08-20 14:13 ` rearnsha at gcc dot gnu.org
2012-09-04 19:43 ` ramana at gcc dot gnu.org
2012-09-07 10:31 ` [Bug tree-optimization/54295] [4.7 Regression] " rguenth at gcc dot gnu.org
2012-09-07 10:37 ` rearnsha at gcc dot gnu.org
2012-09-20 10:18 ` jakub at gcc dot gnu.org
2013-04-11 7:59 ` rguenth at gcc dot gnu.org
2013-04-29 12:56 ` jogo at openwrt dot org [this message]
2014-06-12 13:16 ` rguenth 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-54295-4-TIPFSjTkJ5@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).