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/50678] [4.7 Regression] FAIL: c52104y on x86_64-apple-darwin10
Date: Tue, 18 Oct 2011 15:22:00 -0000 [thread overview]
Message-ID: <bug-50678-4-rCzkPFx4Kt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50678-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50678
--- Comment #44 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-10-18 15:22:14 UTC ---
> Created attachment 25540 [details]
> demonstration of the fault using c++/vendor's tools
>
> after Eric solved my inverted-logic thinko ...
> .. I reproduced using g++-4.2
> bug filed as radar #10302855.
Thanks!
> I think we'll need to apply the patch in the short/medium term and then figure
> out how to control it - which will depend on which system(s) a fix is released
> for.
One approach could be to scan the unwind info of _sigtramp live and check for
the problematic pattern. You call __builtin_return_address from the handler to
get the PC of _sigtramp, then _Unwind_Find_FDE on this PC and you scan starting
from the address you get (the length of the FDE of _sigtramp is 0xc0
currently).
The problematic pattern are the lines:
0x7fff85ccff61: 0x10 0x01 0x05 0x73 0x30 0x06 0x23 0x18
and
0x7fff85ccff71: 0x10 0x03 0x05 0x73 0x30 0x06 0x23 0x28
The register number is the second field (1 or 3) and the offset in the context
is the 8th and last field (0x18 or 0x28). The problem is here if they are in
the same relative order (the likely fix will be to swap 0x18 and 0x28 in the
unwind info).
next prev parent reply other threads:[~2011-10-18 15:22 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 12:56 [Bug ada/50678] New: " dominiq at lps dot ens.fr
2011-10-09 21:00 ` [Bug ada/50678] " ebotcazou at gcc dot gnu.org
2011-10-10 11:29 ` rguenth at gcc dot gnu.org
2011-10-10 15:41 ` dominiq at lps dot ens.fr
2011-10-10 19:34 ` dominiq at lps dot ens.fr
2011-10-10 20:05 ` iains at gcc dot gnu.org
2011-10-10 20:12 ` dominiq at lps dot ens.fr
2011-10-11 6:19 ` [Bug tree-optimization/50678] " ebotcazou at gcc dot gnu.org
2011-10-11 10:46 ` vries at gcc dot gnu.org
2011-10-11 11:02 ` rguenth at gcc dot gnu.org
2011-10-11 11:21 ` ebotcazou at gcc dot gnu.org
2011-10-11 14:48 ` [Bug ada/50678] " vries at gcc dot gnu.org
2011-10-11 15:57 ` iains at gcc dot gnu.org
2011-10-11 18:45 ` iains at gcc dot gnu.org
2011-10-11 20:42 ` mkuvyrkov at gcc dot gnu.org
2011-10-12 11:33 ` dominiq at lps dot ens.fr
2011-10-12 11:40 ` dominiq at lps dot ens.fr
2011-10-12 11:45 ` iains at gcc dot gnu.org
2011-10-12 11:57 ` dominiq at lps dot ens.fr
2011-10-12 12:28 ` iains at gcc dot gnu.org
2011-10-12 13:35 ` iains at gcc dot gnu.org
2011-10-12 13:48 ` iains at gcc dot gnu.org
2011-10-12 14:09 ` iains at gcc dot gnu.org
2011-10-12 14:54 ` iains at gcc dot gnu.org
2011-10-12 18:05 ` ebotcazou at gcc dot gnu.org
2011-10-12 19:57 ` iains at gcc dot gnu.org
2011-10-12 20:09 ` iains at gcc dot gnu.org
2011-10-12 20:56 ` ebotcazou at gcc dot gnu.org
2011-10-12 22:49 ` iains at gcc dot gnu.org
2011-10-12 22:55 ` ebotcazou at gcc dot gnu.org
2011-10-15 19:34 ` [Bug target/50678] " iains at gcc dot gnu.org
2011-10-15 20:49 ` ebotcazou at gcc dot gnu.org
2011-10-15 21:36 ` ebotcazou at gcc dot gnu.org
2011-10-15 22:38 ` iains at gcc dot gnu.org
2011-10-17 9:59 ` iains at gcc dot gnu.org
2011-10-17 12:15 ` iains at gcc dot gnu.org
2011-10-17 15:38 ` ebotcazou at gcc dot gnu.org
2011-10-17 18:07 ` iains at gcc dot gnu.org
2011-10-17 18:29 ` iains at gcc dot gnu.org
2011-10-17 18:39 ` iains at gcc dot gnu.org
2011-10-17 20:37 ` ebotcazou at gcc dot gnu.org
2011-10-17 22:44 ` ebotcazou at gcc dot gnu.org
2011-10-17 22:52 ` iains at gcc dot gnu.org
2011-10-17 23:00 ` ebotcazou at gcc dot gnu.org
2011-10-18 11:08 ` iains at gcc dot gnu.org
2011-10-18 15:22 ` ebotcazou at gcc dot gnu.org [this message]
2011-10-18 15:33 ` iains at gcc dot gnu.org
2011-10-18 16:04 ` ebotcazou at gcc dot gnu.org
2011-10-18 16:24 ` iains at gcc dot gnu.org
2011-10-18 17:07 ` dominiq at lps dot ens.fr
2011-10-18 17:28 ` iains at gcc dot gnu.org
2011-10-18 19:20 ` iains at gcc dot gnu.org
2011-10-18 20:05 ` ebotcazou at gcc dot gnu.org
2011-10-26 19:49 ` simon at pushface dot org
2011-10-26 20:01 ` iains at gcc dot gnu.org
2011-10-26 20:16 ` ebotcazou at gcc dot gnu.org
2011-10-28 12:00 ` iains at gcc dot gnu.org
2011-10-28 12:02 ` iains at gcc dot gnu.org
2011-11-18 13:29 ` iains at gcc dot gnu.org
2011-11-21 9:16 ` iains at gcc dot gnu.org
2011-11-21 9:27 ` iains at gcc dot gnu.org
2011-11-21 9:43 ` ebotcazou at gcc dot gnu.org
2012-03-22 8:51 ` [Bug target/50678] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-06-14 8:29 ` rguenth at gcc dot gnu.org
2012-09-20 10:26 ` jakub at gcc dot gnu.org
2013-01-31 20:48 ` simon at pushface dot org
2013-02-01 18:33 ` georggcc at googlemail dot com
2013-02-01 21:03 ` simon at pushface dot org
2013-02-01 22:02 ` ebotcazou at gcc dot gnu.org
2013-02-02 17:27 ` simon at pushface dot org
2013-02-02 18:38 ` ebotcazou at gcc dot gnu.org
2013-02-02 23:53 ` georggcc at googlemail dot com
2013-02-05 15:34 ` simon at pushface dot org
2013-02-05 17:49 ` ebotcazou at gcc dot gnu.org
2013-02-05 22:38 ` simon at pushface dot org
2013-02-06 8:28 ` ebotcazou at gcc dot gnu.org
2013-02-06 8:45 ` gingold at gcc dot gnu.org
2013-02-06 9:31 ` ebotcazou at gcc dot gnu.org
2013-02-06 19:03 ` dominiq at lps dot ens.fr
2013-02-07 8:34 ` ebotcazou at gcc dot gnu.org
2013-02-07 18:09 ` ebotcazou at gcc dot gnu.org
2013-02-07 18:10 ` ebotcazou at gcc dot gnu.org
2013-02-07 18:11 ` ebotcazou at gcc dot gnu.org
2013-02-07 18:14 ` ebotcazou at gcc dot gnu.org
2013-02-09 18:10 ` georggcc at googlemail 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-50678-4-rCzkPFx4Kt@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).