From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: Richard Henderson <rth@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "jason@redhat.com" <jason@redhat.com>,
Matthew Fortune <Matthew.Fortune@imgtec.com>
Subject: RE: [RFA] Compact EH Patch
Date: Wed, 25 Nov 2015 17:13:00 -0000 [thread overview]
Message-ID: <FD3DCEAC5B03E9408544A1E416F112420192CC82F4@NA-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <55FC6505.8040203@redhat.com>
> -----Original Message-----
> From: Richard Henderson [mailto:rth@redhat.com]
> Sent: Friday, September 18, 2015 3:25 PM
> To: Moore, Catherine; gcc-patches@gcc.gnu.org
> Cc: jason@redhat.com; Matthew Fortune
> Subject: Re: [RFA] Compact EH Patch
>
> > Index: libgcc/libgcc-std.ver.in
> >
> ==========================================================
> =========
> > --- libgcc/libgcc-std.ver.in (revision 226409)
> > +++ libgcc/libgcc-std.ver.in (working copy)
> > @@ -1918,6 +1918,7 @@ GCC_4.6.0 {
> > __morestack_current_segment
> > __morestack_initial_sp
> > __splitstack_find
> > + _Unwind_GetEhEncoding
> > }
> >
> > %inherit GCC_4.7.0 GCC_4.6.0
> > @@ -1938,3 +1939,8 @@ GCC_4.7.0 {
> > %inherit GCC_4.8.0 GCC_4.7.0
> > GCC_4.8.0 {
> > }
> > +
> > +%inherit GCC_4.8.0 GCC_4.7.0
> > +GCC_4.8.0 {
> > + __register_frame_info_header_bases
> > +}
>
> You can't push new symbols into old versions. These have to go into the
> version for the current gcc.
>
> > Index: libstdc++-v3/config/abi/pre/gnu.ver
> >
> ==========================================================
> =========
> > --- libstdc++-v3/config/abi/pre/gnu.ver (revision 226409)
> > +++ libstdc++-v3/config/abi/pre/gnu.ver (working copy)
> > @@ -1909,6 +1909,7 @@ CXXABI_1.3 {
> > __gxx_personality_v0;
> > __gxx_personality_sj0;
> > __gxx_personality_seh0;
> > + __gnu_compact_pr2;
> > __dynamic_cast;
> >
> > # *_type_info classes, ctor and dtor
> > Index: libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
> >
> ==========================================================
> =========
> > --- libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
> (revision 226409)
> > +++ libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
> (working copy)
> > @@ -200,6 +200,7 @@ CXXABI_2.0 {
> > __cxa_vec_new;
> > __gxx_personality_v0;
> > __gxx_personality_sj0;
> > + __gnu_compact_pr2;
> > __dynamic_cast;
> >
> > # std::exception_ptr
>
> Likewise.
>
I'm getting ready to post the updates to this patch -- hopefully, I can still get it in GCC 6.0.
I'm not sure how to tell what the current CXXABI is for these two files. Should it be CXXABI_2.0 for both of these?
Thanks,
Catherine
next prev parent reply other threads:[~2015-11-25 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:07 Moore, Catherine
2015-08-14 19:58 ` Moore, Catherine
2015-09-09 20:45 ` Jason Merrill
2015-09-09 23:53 ` Richard Henderson
2015-09-14 19:32 ` Moore, Catherine
2015-09-18 19:34 ` Richard Henderson
2015-10-05 23:14 ` Moore, Catherine
2015-10-06 16:12 ` Richard Henderson
2015-11-25 17:13 ` Moore, Catherine [this message]
2015-12-01 21:32 ` Moore, Catherine
2015-12-01 21:33 ` Jason Merrill
2015-12-02 13:39 ` Jonathan Wakely
2015-12-13 22:12 ` Moore, Catherine
2015-10-28 16:44 ` Matthew Fortune
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=FD3DCEAC5B03E9408544A1E416F112420192CC82F4@NA-MBX-04.mgc.mentorg.com \
--to=catherine_moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--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).