public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gokhan Kisacikoglu <kisa@centropolisfx.com>
To: Mark Butcher <M_J_BUTCHER@compuserve.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>, gcc <gcc@gcc.gnu.org>
Subject: Re: Tutorial Time
Date: Thu, 13 Jun 2002 09:12:00 -0000	[thread overview]
Message-ID: <3D08C4D1.F6C7BA89@centropolisfx.com> (raw)
In-Reply-To: <200206121847_MC3-1-218-98BF@compuserve.com>


> 3. What does sjij mean ?

Check out the following links;

http://www.rtems.com/rtems/maillistArchives/rtems-users/1999/april/thrd1.html#00016

http://www.rtems.com/rtems/maillistArchives/rtems-users/1999/april/msg00016.html

"D. V. Henkel-Wallace" <gumby@zembu.com> says;

sjlj-exceptions are exceptions implemented via setjump and longjump.  I 
don't advise using them, especially since ELF exceptions should work.

The fact that sjlj-exceptions only work part of the time suggests that
you 
may have a different problem than the exceptions themselves.

Contact him if you need more info, there is also a number of people
there who covered the topic there...

> 5. ... not yet found a mention of the Motorola Mcore being supported ...

Check out the following link: 

http://gcc.gnu.org/gcc-3.0/features.html

Search for Motorola, you will find the following;

	New Targets and Target Specific Improvements:
	o Port of GCC to Motorola's MCore 210 and 340 contributed. 

So, I guess it depends which mcore you are using...

> 7. Am I mad ?

It depends on the observer, everything is relative.

Gokhan

  parent reply	other threads:[~2002-06-13 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 15:48 Mark Butcher
2002-06-13  9:04 ` Richard Henderson
2002-06-13 10:53   ` mike stump
2002-06-13  9:12 ` Gokhan Kisacikoglu [this message]
2002-06-13 16:13 Mark Butcher

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=3D08C4D1.F6C7BA89@centropolisfx.com \
    --to=kisa@centropolisfx.com \
    --cc=M_J_BUTCHER@compuserve.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@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).