[Bug rtl-optimization/66048] [i386] ICE in create_pre_exit when both AVX and MPX are used

["ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66048

--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Ilya Enkovich from comment #2)
> (In reply to Uroš Bizjak from comment #1)
> > There is a *very* picky assert in mode-switching.c that otherwise allows
> > various exceptions when expected sequence:
> > 
> > (set (reg X) ...)
> > 
> > (use (reg X))
> 
> With MPX we have multiple (use (reg X)) and only the last one is examined.
> It is always the one created for bounds.  Simple swap makes it work.  With
> this patch test passes:

Yes, this could also work. BND registers do not (and should not) require any
mode switching, while return reg could need mode switch. So, return reg should
be the last one.
>From gcc-bugs-return-485853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 08 14:49:12 2015
Return-Path: <gcc-bugs-return-485853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87177 invoked by alias); 8 May 2015 14:49:12 -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 86743 invoked by uid 48); 8 May 2015 14:49:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66071] Calling condition variable's notify_all() causes SEGFAULT when the binary is statically linked
Date: Fri, 08 May 2015 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66071-4-jg5jtfjU7z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66071-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: 2015-05/txt/msg00693.txt.bz2
Content-length: 236

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf071

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you run gdb to see where the crash is? This might be a glibc "issue" by
including only part of pthread library.