public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thopre01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/56846] _Unwind_Backtrace on ARM and noexcept
Date: Wed, 12 Nov 2014 18:10:00 -0000	[thread overview]
Message-ID: <bug-56846-4-KxF2mVHMji@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56846-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from thopre01 at gcc dot gnu.org ---
(In reply to Yvan Roux from comment #9)
> Author: yroux
> Date: Mon Oct  6 12:25:14 2014
> New Revision: 215929
> 
> URL: https://gcc.gnu.org/viewcvs?rev=215929&root=gcc&view=rev
> Log:
> /libstdc++-v3/
> 2014-10-06  Yvan Roux  <yvan.roux@linaro.org>
> 
> 	Backport from trunk r215101.
> 	2014-09-10  Tony Wang  <tony.wang@arm.com>
> 
> 	PR target/56846
> 	* libsupc++/eh_personality.cc (PERSONALITY_FUNCTION):
> 	Return with CONTINUE_UNWINDING when the state pattern
> 	contains: _US_VIRTUAL_UNWIND_FRAME | _US_FORCE_UNWIND
> 
> 
> Modified:
>     branches/linaro/gcc-4_9-branch/libstdc++-v3/ChangeLog.linaro
>     branches/linaro/gcc-4_9-branch/libstdc++-v3/libsupc++/eh_personality.cc


Any chance you could backport for 4.8 Yvan? Do you want me to do it? Or are the
release manager against a 4.8 backport?

Best regards,

Thomas
>From gcc-bugs-return-466549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 12 18:25:20 2014
Return-Path: <gcc-bugs-return-466549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19240 invoked by alias); 12 Nov 2014 18:25:20 -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 19219 invoked by uid 48); 12 Nov 2014 18:25:15 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63836] [5 Regression] r217349 caused segfault building 178.galgel from cpu2000
Date: Wed, 12 Nov 2014 18:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63836-4-3xBzGjHVj7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63836-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-11/txt/msg01021.txt.bz2
Content-length: 748

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

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
A simple testcase:

[hjl@gnu-mic-2 delta-fortran]$ cat foo.f90
      SUBROUTINE DTRSM ( NN, NB)
         DO 50 J = NN, 1, -NB
   50    CONTINUE
      end
[hjl@gnu-mic-2 delta-fortran]$
/export/project/git/gcc-regression/master/217349/usr/bin/gfortran -ffixed-form
-ffixed-line-length-132 -DSPEC_CPU2000_LP64 -ffast-math -S  foo.f90 -O2
foo.f90:4:0:

       end
 ^
Error: non-trivial conversion at assignment
unsigned int
integer(kind=4)
_13 = _7;
foo.f90:4:0: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


  parent reply	other threads:[~2014-11-12 18:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 19:40 [Bug libgcc/56846] New: " npl at chello dot at
2014-05-09  6:10 ` [Bug libgcc/56846] " joey.ye at arm dot com
2014-05-09 16:32 ` npl at chello dot at
2014-05-12  4:16 ` joey.ye at arm dot com
2014-05-14 19:00 ` npl at chello dot at
2014-05-16 15:05 ` ramana at gcc dot gnu.org
2014-08-22  6:01 ` joey.ye at arm dot com
2014-08-25  9:39 ` tony.wang at arm dot com
2014-08-25  9:58 ` tony.wang at arm dot com
2014-09-10  4:46 ` thopre01 at gcc dot gnu.org
2014-10-06 12:25 ` yroux at gcc dot gnu.org
2014-11-01 14:26 ` npl at chello dot at
2014-11-12 18:10 ` thopre01 at gcc dot gnu.org [this message]
2014-11-12 18:28 ` yroux at gcc dot gnu.org
2014-11-13  0:05 ` thopre01 at gcc dot gnu.org
2014-11-13  9:09 ` thopre01 at gcc dot gnu.org
2014-11-27 13:59 ` thopre01 at gcc dot gnu.org
2014-11-27 14:10 ` thopre01 at gcc dot gnu.org
2014-12-15 16:58 ` thopre01 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-56846-4-KxF2mVHMji@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).