From: Teemu Torma <tot@trema.com>
To: Jason Merrill <jason@cygnus.com>
Cc: egcs@cygnus.com, law@cygnus.com, wilson@cygnus.com
Subject: [REPOST] MT-safe exception diffs for 971207
Date: Fri, 12 Dec 1997 03:55:00 -0000 [thread overview]
Message-ID: <199712120910.KAA04988@baht.labs.trema.com> (raw)
In-Reply-To: <u9d8j32pxf.fsf@yorick.cygnus.com>
From: Jason Merrill <jason@cygnus.com>
Date: 11 Dec 1997 19:36:28 -0800
In use_eh_context, why are you using copy_rtx on a REG rtx? That's a nop.
I have noticed that there are obsolete moves which are left over while I
have changed the code. I haven't bothered yet to optimize them out.
I'm not sure why you need five functions to handle eh_context.
Convenience, fewer changes to the other code to help merging. No need to
do it that way.
Why do you cast &eh->info and &eh->dynamic_handler_chain to their own
types?
If I understand you correctly, __get_dynamic_handler_chain is not needed
anymore, so it can be taken away. __get_eh_info is there so that the
compiler does not need to know that much of the contents of eh_context.
Teemu
next prev parent reply other threads:[~1997-12-12 3:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712111608.RAA16152.cygnus.egcs@lev.labs.trema.com>
1997-12-11 19:51 ` Jason Merrill
1997-12-11 19:51 ` Jeffrey A Law
1997-12-12 3:55 ` Teemu Torma [this message]
[not found] ` <u9d8j32pxf.fsf.cygnus.egcs@yorick.cygnus.com>
1997-12-12 0:18 ` Jason Merrill
1997-12-12 1:52 ` Teemu Torma
1997-12-12 1:52 ` Jason Merrill
1997-12-12 1:18 ` Teemu Torma
1997-12-12 1:18 ` Jason Merrill
1997-12-12 8:32 ` David Edelsohn
1997-12-11 8:08 Teemu Torma
1997-12-17 5:04 ` Andrey Slepuhin
1997-12-17 5:14 ` Teemu Torma
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=199712120910.KAA04988@baht.labs.trema.com \
--to=tot@trema.com \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=law@cygnus.com \
--cc=wilson@cygnus.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).