public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Krister Walfridsson <cato@df.lth.se>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/4356: Exception handling does not work at all for NetBSD/i386ELF target
Date: Tue, 16 Oct 2001 14:36:00 -0000 [thread overview]
Message-ID: <20011016213601.26602.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/4356; it has been noted by GNATS.
From: Krister Walfridsson <cato@df.lth.se>
To: Richard Henderson <rth@redhat.com>
Cc: <olgerd@pobox.com>, <gcc-gnats@gcc.gnu.org>, <nobody@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: c++/4356: Exception handling does not work at all for NetBSD/i386
ELF target
Date: Tue, 16 Oct 2001 23:31:23 +0200 (MEST)
On Tue, 16 Oct 2001, Richard Henderson wrote:
> On Mon, Oct 15, 2001 at 11:25:45PM +0200, Krister Walfridsson wrote:
> > * config/i386/netbsd-elf.h (ASM_OUTPUT_ADDR_DIFF_ELT): Define.
> > (JUMP_TABLES_IN_TEXT_SECTION): Define.
>
> Err.. This has nothing at all to do with exception handling.
> It has everything to do with switch statements.
Well, in the process of throwing/catching an exception we run some
code. Among other, the function read_encoded_value_with_base() in
eh_personality.cc. And that function has a switch statment...
Sorry for being unclear about the actual failure in my previous mail.
> So what is the actual problem here, given that readonly_data_section
> will fall back to text_section on a.out systems?
But this is not an a.out system...
Actually I have no clue if JUMP_TABLES_IN_TEXT_SECTION is needed, but
the FreeBSD ELF version has a comment claiming it is necessary. And
NetBSD and FreeBSD is nearly identical, so if it is needed by FreeBSD,
then it is needed by NetBSD too...
/Krister
next reply other threads:[~2001-10-16 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 14:36 Krister Walfridsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-15 14:26 Krister Walfridsson
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=20011016213601.26602.qmail@sourceware.cygnus.com \
--to=cato@df.lth.se \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).