From: "H.J. Lu" <hjl.tools@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Jason Merrill <jason@redhat.com>,
gcc-patches@gcc.gnu.org, Richard Henderson <rth@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: PATCH [8/n]: Prepare x32: PR other/48007: Unwind library doesn't work with UNITS_PER_WORD > sizeof (void *)
Date: Thu, 30 Jun 2011 18:19:00 -0000 [thread overview]
Message-ID: <BANLkTikRuXz1RP1LxU8BCEFoT+pNP5e_Jw@mail.gmail.com> (raw)
In-Reply-To: <yddvcvnxkm0.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On Thu, Jun 30, 2011 at 11:03 AM, Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
> "H.J. Lu" <hjl.tools@gmail.com> writes:
>
>>> gcc/
>>>
>>> 2011-06-30 H.J. Lu <hongjiu.lu@intel.com>
>>>
>>> * config.gcc (libgcc_tm_file): Add i386/value-unwind.h for
>>> Linux/x86.
>>>
>>> * system.h (REG_VALUE_IN_UNWIND_CONTEXT): Poisoned.
>>>
>>> * unwind-dw2.c (_Unwind_Context_Reg_Val): New.
>>> (_Unwind_Get_Unwind_Word): Likewise.
>>> (_Unwind_Get_Unwind_Context_Reg_Val): Likewise.
>>> (_Unwind_Context): Use _Unwind_Context_Reg_Val on the reg field.
>>> (SIGNAL_FRAME_BIT): Define if REG_VALUE_IN_UNWIND_CONTEXT is
>>> defined.
>>> (_Unwind_IsExtendedContext): Likewise.
>>> (EXTENDED_CONTEXT_BIT): Don't define if REG_VALUE_IN_UNWIND_CONTEXT
>>> is defined.
>>> (_Unwind_GetGR): Updated.
>>> (_Unwind_SetGR): Likewise.
>>> (_Unwind_GetGRPtr): Likewise.
>>> (_Unwind_SetGRPtr): Likewise.
>>> (_Unwind_SetGRValue): Likewise.
>>> (_Unwind_GRByValue): Likewise.
>>> (__frame_state_for): Likewise.
>>> (uw_install_context_1): Likewise.
>>>
>>> * doc/tm.texi.in: Document REG_VALUE_IN_UNWIND_CONTEXT.
>>> * doc/tm.texi: Regenerated.
>>>
>>> libgcc/
>>>
>>> 2011-06-30 H.J. Lu <hongjiu.lu@intel.com>
>>>
>>> * config/i386/value-unwind.h: New.
>
> Why all those contortions with i386/value-unwind.h? It seems far
> simpler to me to put this into libgcc/config/i386/linux-unwind.h and be
> done with it.
>
I did it this way so that other non-Linux x32 targets can use it.
--
H.J.
next prev parent reply other threads:[~2011-06-30 18:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 17:02 H.J. Lu
2011-06-25 23:34 ` Joseph S. Myers
2011-06-25 23:36 ` H.J. Lu
2011-06-26 20:06 ` Jason Merrill
2011-06-26 20:22 ` Jason Merrill
2011-06-26 21:45 ` H.J. Lu
2011-06-27 2:12 ` Jason Merrill
2011-06-27 3:17 ` H.J. Lu
2011-06-27 15:16 ` Jason Merrill
2011-06-28 19:25 ` H.J. Lu
2011-06-30 14:46 ` Jason Merrill
2011-06-30 14:53 ` H.J. Lu
2011-06-30 15:26 ` Jason Merrill
2011-06-30 16:36 ` H.J. Lu
2011-06-30 17:57 ` H.J. Lu
2011-06-30 18:01 ` H.J. Lu
2011-06-30 18:10 ` Rainer Orth
2011-06-30 18:19 ` H.J. Lu [this message]
2011-06-30 18:42 ` Rainer Orth
2011-06-30 20:14 ` H.J. Lu
2011-06-30 20:24 ` Richard Henderson
2011-06-30 21:51 ` H.J. Lu
2011-07-01 9:03 ` Rainer Orth
2011-07-01 12:51 ` H.J. Lu
2011-07-01 13:37 ` Rainer Orth
2011-07-01 13:42 ` H.J. Lu
2011-07-01 14:03 ` Rainer Orth
2011-07-01 14:06 ` H.J. Lu
2011-07-01 14:25 ` Rainer Orth
2011-07-01 14:55 ` H.J. Lu
2011-08-02 21:02 ` Jason Merrill
2011-08-02 22:27 ` H.J. Lu
2011-08-03 21:47 ` Jason Merrill
2011-06-30 20:59 ` H.J. Lu
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=BANLkTikRuXz1RP1LxU8BCEFoT+pNP5e_Jw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=rth@redhat.com \
/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).