From: pavenis@lanet.lv
To: "Mark E." <snowball3@bigfoot.com>,
djgpp-workers@delorie.com, binutils@sourceware.cygnus.com,
djgpp-workers@delorie.com
Subject: Re: patch for i386go32.c
Date: Tue, 10 Aug 1999 09:58:00 -0000 [thread overview]
Message-ID: <B0000097729@stargate.astr.lu.lv> (raw)
In-Reply-To: <199908101321.NAA93518@out4.ibm.net>
On 10 Aug 99, at 9:22, Mark E. wrote:
> > + ${RELOCATING+*(.gcc_exc*)
> > + ___EH_FRAME_BEGIN__ = . ;
> > + *(.eh_fram*)
> > + ___EH_FRAME_END__ = . ;
> > + LONG(0)};
> > I checked this in.
>
> Thanks once again.
>
> >
> > However, I'll note that none of the other targets see the need to
> > define __EH_FRAME_{BEGIN,END}__, or to add the LONG(0). That's
> > because other targets use the gcc crtbegin/crtend support. Why not
> > make DJGPP work like other gcc targets?
> >
>
> I wasn't around when it was decided how to handle g++ exceptions. I've added djgpp-
> workers in hopes that someone who was around then there has an answer.
>
This approach were used since port of gcc-2.8.1 (Robert Hoehne)
suggested it as far as I remeber.
Once I tried crtbegin, crtend with egcs-1.1.... (I don't remeber which
exactly) and I had problems (at least I remember so). Maybe it's
time to try once more.
Andris
prev parent reply other threads:[~1999-08-10 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-09 15:59 Mark E.
1999-08-09 20:08 ` Ian Lance Taylor
1999-08-10 6:22 ` Mark E.
1999-08-10 9:58 ` pavenis [this message]
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=B0000097729@stargate.astr.lu.lv \
--to=pavenis@lanet.lv \
--cc=binutils@sourceware.cygnus.com \
--cc=djgpp-workers@delorie.com \
--cc=snowball3@bigfoot.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).