public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: sxthree@penfeld.tls.mms.fr (SXTHREE)
To: egcs@cygnus.com
Subject: Exception handling and VxWorks
Date: Tue, 24 Mar 1998 11:16:00 -0000	[thread overview]
Message-ID: <199803240854.JAA19006@penfeld.tls.mms.fr> (raw)

	It seems EH will be MT safe in the release 1.1
of egcs. What about multi-task safety in a VxWorks environnement ?

	I had problems building egcs 1.0.2 for the PowerPC-VxWorks target:
I tried to use to use binutils 2.8.0.15 for targets powerPC-wrs-elf32 and
powerPC-wrs-eabi with egcs targets powerPC-wrs-vxworks5.3.
1- eabi.S does not compile complaining about relocations. I guess
   RELOCATABLE should be defined when using -mrelocatable-lib flag,
   it is not.
2- Lots of problems with stdargs.

Using elf32 targets for both binutils and egcs targets seems to work fine,
but EH is not safe.

F. Michel sxthree@penfeld.tls.mms.fr

             reply	other threads:[~1998-03-24 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-24 11:16 SXTHREE [this message]
1998-03-27  4:21 ` Jeffrey A Law
1998-03-26 17:15 Mike Stump
1998-03-30 16:18 Mike Stump

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=199803240854.JAA19006@penfeld.tls.mms.fr \
    --to=sxthree@penfeld.tls.mms.fr \
    --cc=egcs@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).