From: NightStrike <nightstrike@gmail.com>
To: "Nick Clifton" <nickc@redhat.com>
Cc: "Kai Tietz" <Kai.Tietz@onevision.com>, "H. J. Lu" <hjl@lucon.org>,
binutils@sources.redhat.com
Subject: Re: PATCH: w64 native support
Date: Tue, 24 Jul 2007 08:00:00 -0000 [thread overview]
Message-ID: <b609cb3b0707232121m1d058deexc50d1092976855d6@mail.gmail.com> (raw)
In-Reply-To: <4695D6FC.2070406@redhat.com>
On 7/12/07, Nick Clifton <nickc@redhat.com> wrote:
> Hi Kai,
>
> In the better late than never category we have...
>
> > 2007-04-18 Kai Tietz <kai.tietz@onevision.com>
> >
> > * bfd/bfd-in.h: (BFD_HOST_64BIT_LONG_LONG): New
> > as equivalent for BFD_HOST_64BIT_LONG.
> > (BFD_HOSTPTR_T): Host pointer type for casting a
> > pointer to an integer type.
> > (bfd_hostptr_t): The typedef of BFD_HOSTPTR_T.
> > (sprintf_vma, fprintf_vma): Add support for long long prints.
> > * bfd/bfd-in2.h: Regenerate.
> > * bfd/configure.in: (BFD_HOST_64BIT_LONG_LONG): New
> > as equivalent for BFD_HOST_64BIT_LONG.
> > (BFD_HOSTPTR_T): Host pointer type for casting a
> > pointer to an integer type. Defauls is "unsigned long".
> > (AC_CHECK_SIZEOF(void *)): New.
> > (host64): Set it if the pointer size is 8.
> > * bfd/configure: Regenerate.
> > * bfd/config.in: Add macro SIZEOF_VOID_P.
> > * bfd/coffcode.h: Replace host ptr type assuming "long" to
> > bfd_hostptr_t type.
> > * bfd/coffgen.c: Likewise.
> > * bfd/elf-eh-frame.c: Likewise.
> > * bfd/peicode.h: Likewise.
> > * gas/symbols.c: Print bfd_hostptr_t to file via fprintf_vma.
> > * gas/write.c: Likewise.
> > * gprof/cg_print.c: Force cast of sizeof to be a long.
> > * gprof/hist.c: Likewise.
> > * include/splay-tree.h: New type libi_uhostptr_t needed for
> > w64 when a long is not wide enought for a pointer for
> > splay_tree_key and splay_tree_value..
> > (splay_tree_key, splay_tree_value): As above, see comment.
> > * include/coff/internal.h: Replace host ptr type assuming "long"
> > to bfd_hostptr_t type.
> > * libiberty/strerror.c: Undefine sys_nerr and sys_errlist if
> > allready defined in front by runtime headers.
>
> I have now checked all of this patch in, apart from the change to
> libiberty. You will need to submit that one separately to the libiberty
> maintainers.
>
> Cheers
> Nick
>
Does anyone know if this made it into libiberty?
next prev parent reply other threads:[~2007-07-24 4:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 13:43 Kai Tietz
2007-04-11 13:58 ` H. J. Lu
2007-04-11 14:07 ` H. J. Lu
2007-04-11 18:22 ` PATCH: windres Kai Tietz
2007-04-12 15:55 ` H. J. Lu
2007-04-12 16:51 ` Kai Tietz
2007-04-12 18:03 ` H. J. Lu
2007-04-13 14:41 ` Kai Tietz
2007-04-13 14:49 ` H. J. Lu
2007-04-16 10:05 ` Kai Tietz
2007-04-16 21:59 ` Christopher Faylor
2007-04-16 22:20 ` H. J. Lu
2007-04-17 10:59 ` Kai Tietz
2007-04-18 4:34 ` Christopher Faylor
2007-04-18 9:49 ` H. J. Lu
2007-04-20 13:34 ` Kai Tietz
2007-04-20 13:35 ` H. J. Lu
2007-04-20 13:54 ` Kai Tietz
2007-04-20 14:03 ` H. J. Lu
2007-04-20 13:40 ` Dave Korn
2007-04-20 13:51 ` Kai Tietz
2007-04-20 13:58 ` Dave Korn
2007-04-23 12:26 ` Kai Tietz
2007-04-23 12:44 ` Christopher Faylor
2007-04-23 13:51 ` Kai Tietz
2007-04-23 14:23 ` Christopher Faylor
2007-04-23 14:36 ` Dave Korn
2007-04-23 14:46 ` Kai Tietz
2007-04-23 14:50 ` Christopher Faylor
2007-04-18 11:59 ` PATCH: w64 native support Kai Tietz
2007-06-29 5:37 ` NightStrike
2007-07-12 7:30 ` Nick Clifton
2007-07-24 8:00 ` NightStrike [this message]
2007-04-11 14:57 ` Kai Tietz
2007-04-11 15:17 ` Daniel Jacobowitz
2007-04-11 15:24 ` Kai Tietz
2007-04-11 15:43 ` Daniel Jacobowitz
2007-04-11 15:49 ` Kai Tietz
2007-04-11 17:34 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-04-10 16:06 Kai Tietz
2007-04-10 16:13 ` H. J. Lu
2007-04-10 16:23 ` Kai Tietz
2007-04-10 17:01 ` Kai Tietz
2007-04-10 17:18 ` H. J. Lu
2007-04-10 17:52 ` Kai Tietz
2007-04-10 19:35 ` H. J. Lu
2007-04-11 3:40 ` H. J. Lu
2007-04-10 20:55 ` Paul Koning
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=b609cb3b0707232121m1d058deexc50d1092976855d6@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=Kai.Tietz@onevision.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=nickc@redhat.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).