From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: gcc-patches@gcc.gnu.org
Cc: Olivier Hainque <hainque@adacore.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: [RFC PATCH 0/6] some vxworks/powerpc patches
Date: Mon, 04 Jun 2018 14:46:00 -0000 [thread overview]
Message-ID: <20180604144626.5902-1-rasmus.villemoes@prevas.dk> (raw)
These are some of the patches I'm currently applying to get a full C
and C++ compiler to work for powerpc-wrs-vxworks (for vxworks
5.5). With these, and a few more, I have ZCX, static
constuctors/destructors and throwing across modules working. There are
many vxworks variants out there, so I'm not sure how to avoid breaking
things for others. I don't really like the crti hack, but I don't have
any better ideas (I can probably patch the loader to recognize even
symbols of type unknown, but that won't benefit anybody else, so I'm
trying to fix problems in gcc whenever possible).
Rasmus Villemoes (6):
vxworks: add target/h/wrn/coreip to the set of system include paths
libgcc: add crt{begin,end} for powerpc-wrs-vxworks target
vxworks: enable use of .init_array/.fini_array for cdtors
powerpc/vxworks: [hack] add crti.o file
powerpc/vxworks: add {START,END}FILE_SPEC for
HAVE_INITFINI_ARRAY_SUPPORT
vxworks: don't define vxworks_asm_out_constructor when using
.init_array
gcc/config/rs6000/vxworks.h | 13 +++++++++++--
gcc/config/vxworks.c | 9 +++++++--
gcc/config/vxworks.h | 20 ++++++++++++++------
libgcc/config.host | 3 ++-
libgcc/config/rs6000/t-vxworks | 5 +++++
libgcc/config/rs6000/vxworks-crti.S | 10 ++++++++++
6 files changed, 49 insertions(+), 11 deletions(-)
create mode 100644 libgcc/config/rs6000/t-vxworks
create mode 100644 libgcc/config/rs6000/vxworks-crti.S
--
2.15.1
next reply other threads:[~2018-06-04 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:46 Rasmus Villemoes [this message]
2018-06-04 14:46 ` [RFC PATCH 3/6] vxworks: enable use of .init_array/.fini_array for cdtors Rasmus Villemoes
2018-06-04 14:46 ` [RFC PATCH 6/6] vxworks: don't define vxworks_asm_out_constructor when using .init_array Rasmus Villemoes
2018-06-04 14:46 ` [RFC PATCH 1/6] vxworks: add target/h/wrn/coreip to the set of system include paths Rasmus Villemoes
2018-06-12 21:12 ` Jeff Law
2018-06-12 21:34 ` Olivier Hainque
2018-06-13 6:46 ` Rasmus Villemoes
2018-06-14 8:40 ` Olivier Hainque
2018-06-04 14:46 ` [RFC PATCH 2/6] libgcc: add crt{begin,end} for powerpc-wrs-vxworks target Rasmus Villemoes
2018-06-04 14:46 ` [RFC PATCH 4/6] powerpc/vxworks: [hack] add crti.o file Rasmus Villemoes
2018-06-04 14:46 ` [RFC PATCH 5/6] powerpc/vxworks: add {START,END}FILE_SPEC for HAVE_INITFINI_ARRAY_SUPPORT Rasmus Villemoes
2018-06-19 16:46 ` [RFC PATCH 0/6] some vxworks/powerpc patches Olivier Hainque
2018-06-26 12:46 ` Rasmus Villemoes
2018-06-27 8:31 ` Olivier Hainque
2018-06-28 8:43 ` [PATCH v2 0/4] " Rasmus Villemoes
2018-06-28 8:43 ` [PATCH v2 4/4] vxworks: don't define vxworks_asm_out_constructor when using .init_array Rasmus Villemoes
2018-08-13 12:53 ` Olivier Hainque
2018-06-28 8:43 ` [PATCH v2 1/4] vxworks: add target/h/wrn/coreip to the set of system include paths Rasmus Villemoes
2018-08-06 12:12 ` Olivier Hainque
2018-08-06 12:19 ` Olivier Hainque
2018-06-28 8:43 ` [PATCH v2 3/4] vxworks: enable use of .init_array/.fini_array for cdtors Rasmus Villemoes
2018-08-10 15:59 ` Olivier Hainque
2018-08-13 8:25 ` Rasmus Villemoes
2018-08-13 11:54 ` Olivier Hainque
2018-06-28 8:43 ` [PATCH v2 2/4] libgcc: add crt{begin,end} for powerpc-wrs-vxworks target Rasmus Villemoes
2018-08-16 9:30 ` Rasmus Villemoes
2018-08-17 19:30 ` Olivier Hainque
2018-08-03 12:37 ` [PATCH v2 0/4] some vxworks/powerpc patches Olivier Hainque
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=20180604144626.5902-1-rasmus.villemoes@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.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).