From: "David Lanzendörfer" <leviathan@libresilicon.com>
To: binutils@sourceware.org
Subject: Re: [PATCH 0/2] Introducing support for cross compiling/linking for the z/OS platform
Date: Sun, 26 Jan 2020 15:50:00 -0000 [thread overview]
Message-ID: <10133195.aW3RaaTnYq@dizzy-7> (raw)
In-Reply-To: <20200126113756.2009-1-leviathan@libresilicon.com>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
Ignore this one
On Sunday, 26 January 2020 7:37:52 PM HKT David Lanzenörfer wrote:
> From: David Lanzendörfer <leviathan@libresilicon.com>
>
> Dear mailing list
>
> Please discard the last patchset, this one is the correct one ^^'
> The file bfd/po-s390.h is of course not needed and has slipped in from a
> rebased old patchset.
>
> I've been refurbishing the work from Ambitus, an attempt by the Linux
> Foundation to support cross compiling for the z/OS mainframe platform with
> GCC.
>
> The following two patches are needed to create executable headers which
> allows to execute binaries on the z/OS platform.
>
> Patchsets for GCC itself will follow soon on the GCC developer mailing list,
> since I'm still cleaning up and debugging those.
>
> Linking however already works without any issues, so I already submit those.
>
> David Lanzendörfer (2):
> z/OS Support: Catching segfaults
> z/OS support: Introducing z/OS support
>
> bfd/bfd-in2.h | 1 +
> bfd/config.bfd | 5 +
> bfd/configure | 1 +
> bfd/configure.ac | 1 +
> bfd/linker.c | 2 +-
> bfd/po-bfd.h | 93 ++
> bfd/po64-s390.c | 1697 +++++++++++++++++++++++++++++++++++
> bfd/targets.c | 1 +
> config.sub | 6 +-
> gas/configure.tgt | 1 +
> include/po/common.h | 167 ++++
> include/po/external.h | 324 +++++++
> include/po/internal.h | 187 ++++
> ld/Makefile.am | 7 +-
> ld/Makefile.in | 8 +-
> ld/configure.tgt | 3 +
> ld/emulparams/po64_s390.sh | 109 +++
> ld/ldlang.c | 4 +
> ld/scripttempl/po64_s390.sc | 12 +
> 19 files changed, 2625 insertions(+), 4 deletions(-)
> create mode 100644 bfd/po-bfd.h
> create mode 100644 bfd/po64-s390.c
> create mode 100644 include/po/common.h
> create mode 100644 include/po/external.h
> create mode 100644 include/po/internal.h
> create mode 100644 ld/emulparams/po64_s390.sh
> create mode 100644 ld/scripttempl/po64_s390.sc
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-01-26 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 11:38 David Lanzenörfer
2020-01-26 11:38 ` [PATCH 2/2] z/OS support: Introducing z/OS support David Lanzenörfer
2020-01-27 8:42 ` Alan Modra
2020-01-28 7:37 ` David Lanzendörfer
2020-01-26 11:38 ` [PATCH 1/2] " David Lanzenörfer
2020-01-26 11:38 ` [PATCH 1/2] z/OS Support: Catching segfaults David Lanzenörfer
2020-01-27 7:18 ` Alan Modra
2020-01-28 7:39 ` David Lanzendörfer
2020-01-26 11:38 ` [PATCH 2/2] " David Lanzenörfer
2020-01-26 15:50 ` David Lanzendörfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-26 11:43 [PATCH 0/2] Introducing support for cross compiling/linking for the z/OS platform David Lanzenörfer
2020-02-10 15:49 ` Nick Clifton
2020-01-26 11:33 David Lanzenörfer
2020-01-26 15:50 ` David Lanzendörfer
2020-01-26 23:46 ` Hans-Peter Nilsson
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=10133195.aW3RaaTnYq@dizzy-7 \
--to=leviathan@libresilicon.com \
--cc=binutils@sourceware.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).