From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: Al_Niessner@bigfoot.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc symbol names
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200003020911.KAA00715@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.FOsfwMkaW5xbR_5QvBi3xw5ZQ-oupHb55UzIFILo8-Q@z> (raw)
In-Reply-To: <38BDDFE3.B53E2520@bigfoot.com>
> I asked around about VxWorks handling the ctors section and the prevailing
> thought was no it won't.
In that case, it looks like a genuine bug in the VxWorks configuration
files of the official gcc. WindRiver may be using different
configuration files - it might be worthwhile checking their
sources. I'm not sure what the bottom of the problem is - I see
vxppc.h includes rs6000/sysv4.h. Perhaps there are other features
claimed to work by sysv4.h which aren't available in VxWorks?
Anyway, would you care to produce a patch for gcc to fix this bug?
Please send it to gcc-patches@gcc.gnu.org.
Regards,
Martin
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-29 20:05 Al Niessner
2000-03-01 1:18 ` Martin v. Loewis
2000-03-01 19:26 ` Al Niessner
2000-03-02 1:18 ` Martin v. Loewis [this message]
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Al Niessner
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Al Niessner
-- strict thread matches above, loose matches on Subject: below --
2000-02-26 20:29 Al Niessner
2000-02-27 11:21 ` Martin v. Loewis
2000-02-27 12:17 ` Al Niessner
2000-02-27 12:58 ` Martin v. Loewis
2000-02-27 18:51 ` Al Niessner
2000-02-28 1:32 ` Martin v. Loewis
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Al Niessner
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Al Niessner
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Al Niessner
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=200003020911.KAA00715@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=Al_Niessner@bigfoot.com \
--cc=gcc-help@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).