This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[Bug target/72788] New: Stack unwinding fails since GCC 4.9 on i686 without -fexceptions

From: "fw at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
To: gcc-bugs at gcc dot gnu dot org
Date: Wed, 03 Aug 2016 12:42:53 +0000
Subject: [Bug target/72788] New: Stack unwinding fails since GCC 4.9 on i686 without -fexceptions
Auto-submitted: auto-generated

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

            Bug ID: 72788
           Summary: Stack unwinding fails since GCC 4.9 on i686 without
                    -fexceptions
           Product: gcc
           Version: 7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fw at gcc dot gnu.org
  Target Milestone: ---
            Target: i686-redhat-linux-gnu

The tst-cleanupx4 test case used to test stack unwinding (for thread
cancellation processing) for code compiled without -fexceptions.  Starting with
GCC 4.9, this no longer works on i686:

  https://www.sourceware.org/ml/libc-alpha/2014-07/msg00299.html
  https://www.sourceware.org/ml/libc-alpha/2015-11/msg00533.html

Is the requirement for -fexceptions expected behavior on the GCC side?

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]