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 rtl-optimization/58679] [4.9 regression] ICE in create_pre_exit, at mode-switching.c:421 with -mavx after r202915
Date: Sat, 26 Oct 2013 16:05:00 -0000	[thread overview]
Message-ID: <bug-58679-4-R0NpP0WIIP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58679-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58679

--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Eric Botcazou from comment #8)
> > Or should we use a different approach, and use DF to re-create REG_DEAD
> > notes?
> 
> Yes, if you need REG_DEAD/REG_UNUSED notes, just tell DF to compute them:

I think that missing REG_DEAD/REG_UNUSED notes and r202915 just triggered the
problem, fixed with [1] - at least I'm not able to trigger the ICE described in
Comment #0 anymore.

The new problem was introduced by Vladimir's patch that removed final
assignments to return registers in several cases. The postreload mode-switching
pass depends on them, and gcc.target/i386/{avx-1,sse-23,sse-24}.c testcases
start to fail on x86 [2]. Also, bootstrap will be broken when configured with
"--with-arch=core-avx-i --with-cpu=core-avx-i --with-fpmath=avx" due to
post-reload mode switching failures in libjava and libgo.


[1] http://gcc.gnu.org/ml/gcc-patches/2013-10/msg01606.html
[2] http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg02051.html
>From gcc-bugs-return-432794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Oct 26 16:12:14 2013
Return-Path: <gcc-bugs-return-432794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21194 invoked by alias); 26 Oct 2013 16:12:14 -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 21160 invoked by uid 48); 26 Oct 2013 16:12:09 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58804] dynamic_bitset<> uses popcountl on long long
Date: Sat, 26 Oct 2013 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.7.4
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-58804-4-xbilV0yuI8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58804-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: 2013-10/txt/msg01938.txt.bz2
Content-length: 291

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX804

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.9.0


  parent reply	other threads:[~2013-10-26 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  8:46 [Bug rtl-optimization/58679] New: " izamyatin at gmail dot com
2013-10-10 12:02 ` [Bug rtl-optimization/58679] " rguenth at gcc dot gnu.org
2013-10-26  7:38 ` ubizjak at gmail dot com
2013-10-26 11:42 ` ubizjak at gmail dot com
2013-10-26 13:25 ` amylaar at gcc dot gnu.org
2013-10-26 14:35 ` ubizjak at gmail dot com
2013-10-26 16:05 ` ubizjak at gmail dot com [this message]
2013-10-26 16:13 ` amylaar at gcc dot gnu.org
2013-10-26 16:20 ` ebotcazou at gcc dot gnu.org
2013-10-26 16:22 ` amylaar at gcc dot gnu.org
2013-10-27 20:57 ` 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-58679-4-R0NpP0WIIP@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).