public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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: Tue, 07 Feb 2012 16:59:00 -0000	[thread overview]
Message-ID: <bug-51921-4-ZESwuDNxHQ@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

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-02-07 16:59:32 UTC ---
> --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-07 15:37:54 UTC ---
> Only sparc-sun-solaris2.10 is a primary target at the moment.  Rainer, you
> say "regression from 4.6" but the summary says 4.6/4.7 regression, not 4.7
> regression.  No known-to-work/known-to-fail field.  Does this only affect Ada?
>
> Please clarify.

I'd only noticed the breakage on mainline at first, but Eric reverted
the patch to support Solaris 11 on both mainline and the 4.6 branch, so
it indeed regressed on both branches.

It doesn't affect only Ada, but Java, too, which chooses to ignore.

I'm quite upset about this because the only reason for that reversion
he's given so far is a failure (I wouldn't call it regression) on a
7-year-old Solaris 10 beta release (or rather, one of many two-weekly
builds).  AFAICT, no released version is affected by my rewrite of
sparc/sol2-unwind.h, which introduced Solaris 11 support before 4.6.0,
which is now completely broken.

I don't buy his compatibility argument for several reasons:

* Even Sun/Oracle makes no compatibility guarantee of any sort for
  betas, and can break it if need we.  I don't see us making stronger
  guarantees in FSF GCC, especially to keep prehistoric betas working at
  the expense of the latest shipping release.

* Such versions are completely untestable: I've been in the Solaris 10
  Express and Platinum Beta programs myself, and ran practically every
  single one of those bi-weekly builds (that's what s10_72 is) on my
  machines, but didn't keep the ISO images for space reasons.

* If some AdaCore customer couldn't be bothered to upgrade to a release
  (I'm talking about any release here, not supported or latest) version
  of Solaris in 7 years, but needs to run bleeding-edge versions of GCC,
  I declare that AdaCore's problem, not mine.  If the only ill effect of
  a patch of mine is to break such ancient beta versions (not
  intentionally or lightly), so be it.  I'm not jumping through hoops to
  fix that.

I'm sort of tempted to revert Eric's reversion to restore working
Solaris 11 support in 4.6 and mainline, but would only do that as a very
last resort.

    Rainer


  parent reply	other threads:[~2012-02-07 16:59 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 ` [Bug target/51921] [4.6/4.7 regression] EH unwinding support is broken ebotcazou at gcc dot gnu.org
2012-02-07 15:38 ` rguenth at gcc dot gnu.org
2012-02-07 16:59 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
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-ZESwuDNxHQ@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).