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 middle-end/61111] [4.10 regression] Infinite recursion between fold_build2_stat_loc and fold_binary_loc
Date: Fri, 09 May 2014 11:29:00 -0000 [thread overview]
Message-ID: <bug-61111-4-9NzvZqkPJa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61111-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61111
Kenneth Zadeck <zadeck at naturalbridge dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zadeck at naturalbridge dot com
--- Comment #8 from Kenneth Zadeck <zadeck at naturalbridge dot com> ---
Created attachment 32767
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32767&action=edit
patch to fix.
I agree with richi that the mask should have been w bits wide.
I test the patch on x86_64 last night and it causes no harm.
ok to commit?
next prev parent reply other threads:[~2014-05-09 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:44 [Bug middle-end/61111] New: " rearnsha at gcc dot gnu.org
2014-05-08 13:56 ` [Bug middle-end/61111] " ktkachov at gcc dot gnu.org
2014-05-08 14:19 ` rearnsha at gcc dot gnu.org
2014-05-08 14:32 ` rearnsha at gcc dot gnu.org
2014-05-08 14:43 ` [Bug middle-end/61111] [4.10 regression] " rguenth at gcc dot gnu.org
2014-05-08 14:44 ` rguenth at gcc dot gnu.org
2014-05-09 2:37 ` mrs at gcc dot gnu.org
2014-05-09 11:05 ` rguenth at gcc dot gnu.org
2014-05-09 11:29 ` zadeck at naturalbridge dot com [this message]
2014-05-09 11:35 ` rguenther at suse dot de
2014-05-09 12:22 ` zadeck at gcc dot gnu.org
2014-05-09 12:30 ` zadeck at naturalbridge dot com
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-61111-4-9NzvZqkPJa@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).