public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63702] i386.c:36276: possible missing break ?
Date: Fri, 31 Oct 2014 18:51:00 -0000 [thread overview]
Message-ID: <bug-63702-4-ORvkP2Is22@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63702-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63702
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to David Binderman from comment #0)
> [gcc/config/i386/i386.c:36276] -> [gcc/config/i386/i386.c:36338]: (warning)
> Vari
> able 'nargs' is reassigned a value before the old one has been used.
> 'break;' mi
> ssing?
>
> case QI_FTYPE_V4DI_V4DI_QI:
> case V4SF_FTYPE_V2DF_V4SF_QI:
> case V4SF_FTYPE_V4DF_V4SF_QI:
> nargs = 3;
> case V16SI_FTYPE_V16SI_V16SI_HI:
> case V16SI_FTYPE_V16SI_V16SI_V16SI:
> case V16SI_FTYPE_V4SI_V16SI_HI:
No, this assignment should just be removed. I'll take care for this.
>From gcc-bugs-return-465511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Oct 31 18:51:24 2014
Return-Path: <gcc-bugs-return-465511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10995 invoked by alias); 31 Oct 2014 18:51:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10945 invoked by uid 48); 31 Oct 2014 18:51:18 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63620] RELOAD lost SET_GOT dependency on Darwin
Date: Fri, 31 Oct 2014 19:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vmakarov at redhat dot com
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63620-4-9xWdehv4RU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-10/txt/msg02532.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc620
--- Comment #21 from Jeffrey A. Law <law at redhat dot com> ---
Uros,
Any objection to installing that patch to work around these problems while Vlad
works on things from the rematerialization side?
Perhaps put that condition in a function which makes it clear that this is just
a workaround to give Vlad time to build out the real solution?
next prev parent reply other threads:[~2014-10-31 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:39 [Bug target/63702] New: " dcb314 at hotmail dot com
2014-10-31 18:51 ` ubizjak at gmail dot com [this message]
2014-10-31 21:59 ` [Bug target/63702] " uros at gcc dot gnu.org
2014-10-31 22:09 ` ubizjak at gmail 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-63702-4-ORvkP2Is22@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).