public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53038] cfi_restore for cr before cr is actually restored Date: Thu, 19 Apr 2012 07:34:00 -0000 [thread overview] Message-ID: <bug-53038-4-r7aGHNSFS1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53038-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53038 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |powerpc-linux Known to fail| |4.5.5, 4.6.4, 4.7.1, 4.8.0 --- Comment #1 from Alan Modra <amodra at gmail dot com> 2012-04-19 07:32:30 UTC --- Earlier compilers without shrink-wrap on by default need -fasynchronous-unwind-tables to get the epilogue cfi_restores.
next prev parent reply other threads:[~2012-04-19 7:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-19 7:21 [Bug target/53038] New: " amodra at gmail dot com 2012-04-19 7:34 ` amodra at gmail dot com [this message] 2012-04-19 15:34 ` [Bug target/53038] " amodra at gmail dot com 2012-04-19 15:35 ` amodra at gmail dot com 2012-05-01 4:04 ` amodra at gcc dot gnu.org 2013-02-06 3:05 ` amodra 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-53038-4-r7aGHNSFS1@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: linkBe 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).