public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51921] [4.6/4.7 regression] EH unwinding support is broken
Date: Fri, 20 Jan 2012 19:32:00 -0000 [thread overview]
Message-ID: <bug-51921-4-dYUTVpfgtu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51921-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51921
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-01-20
Target Milestone|--- |4.6.3
Summary|[4.7 regression] EH |[4.6/4.7 regression] EH
|unwinding support is broken |unwinding support is broken
|on Solaris 11 |
Ever Confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-01-20 19:15:14 UTC ---
With this line of reasoning, there was no real justification for rewriting it
from scratch either... This code is used in Ada (I don't count Java here, as
nobody uses GCJ on SPARC/Solaris) and the emphasis in Ada is robustness; we
cannot afford introducing gratuitous regressions (and I certainly don't want to
maintain a separate code for AdaCore's compiler) so we need to find a modus
vivendi.
next prev parent reply other threads:[~2012-01-20 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:37 [Bug target/51921] New: [4.7 regression] EH unwinding support is broken on Solaris 11 ro at gcc dot gnu.org
2012-01-20 19:32 ` ebotcazou at gcc dot gnu.org [this message]
2012-02-07 15:38 ` [Bug target/51921] [4.6/4.7 regression] EH unwinding support is broken rguenth at gcc dot gnu.org
2012-02-07 16:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-07 17:12 ` ebotcazou at gcc dot gnu.org
2012-02-07 17:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-07 17:55 ` ebotcazou at gcc dot gnu.org
2012-02-08 10:45 ` rguenth at gcc dot gnu.org
2012-02-08 18:04 ` ro at gcc dot gnu.org
2012-02-08 18:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-10 23:35 ` pinskia at gcc dot gnu.org
2012-02-10 23:37 ` pinskia at gcc dot gnu.org
2012-02-11 0:10 ` ian at airs dot com
2012-02-11 10:51 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:18 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:19 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:19 ` ebotcazou 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-51921-4-dYUTVpfgtu@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).