public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37610] [4.4 Regression] FAIL: g++.dg/eh/pr29166.C execution test Date: Tue, 18 Nov 2008 09:05:00 -0000 [thread overview] Message-ID: <20081118090355.23116.qmail@sourceware.org> (raw) In-Reply-To: <bug-37610-276@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jakub at gcc dot gnu dot org 2008-11-18 09:03 ------- libunwind also scales all of DW_CFA_advance_loc{,1,2,4} by code alignment factor and IMHO it matches the standard wording too: DW_CFA_advance_loc The DW_CFA_advance instruction takes a single operand (encoded with the opcode) that represents a constant delta. The required action is to create a new table row with a location value that is computed by taking the current entry's location value and adding the value of delta * code_alignment_factor. All other values in the new row are initially identical to the current row. DW_CFA_advance_loc1 The DW_CFA_advance_loc1 instruction takes a single ubyte operand that represents a constant delta. This instruction is identical to DW_CFA_advance_loc except for the encoding and size of the delta operand. Can you submit the trivial fix (replace 3 times (delta) with (scaled) in dw2gencfi.c to binutils? On the GCC side we'll need to write a configury test which will fail if this bug is detected and the target has code alignment factor bigger than 1. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37610
next prev parent reply other threads:[~2008-11-18 9:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-21 16:08 [Bug target/37610] New: " danglin at gcc dot gnu dot org 2008-09-28 23:47 ` [Bug target/37610] " pinskia at gcc dot gnu dot org 2008-10-22 3:11 ` mmitchel at gcc dot gnu dot org 2008-11-18 1:23 ` danglin at gcc dot gnu dot org 2008-11-18 2:33 ` danglin at gcc dot gnu dot org 2008-11-18 9:05 ` jakub at gcc dot gnu dot org [this message] 2008-11-18 9:21 ` jakub at gcc dot gnu dot org 2008-11-18 14:08 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-18 14:57 ` danglin at gcc dot gnu dot org 2008-11-18 18:50 ` ebotcazou at gcc dot gnu dot org 2008-11-18 18:52 ` ebotcazou at gcc dot gnu dot org 2008-11-29 21:07 ` jakub at gcc dot gnu dot org 2008-12-02 15:49 ` jakub at gcc dot gnu dot org 2008-12-03 9:12 ` jakub at gcc dot gnu dot org 2008-12-03 9:18 ` jakub at gcc dot gnu dot org 2008-12-20 22:35 ` ebotcazou at gcc dot gnu dot 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=20081118090355.23116.qmail@sourceware.org \ --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).