public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, gdb@sourceware.org, siddhesh@redhat.com
Subject: Re: Old OSes compatibility  [Re: 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST]
Date: Mon, 01 Oct 2012 17:55:00 -0000	[thread overview]
Message-ID: <20121001175455.GA3955@host2.jankratochvil.net> (raw)
In-Reply-To: <83d312ayjy.fsf@gnu.org>

On Mon, 01 Oct 2012 19:32:01 +0200, Eli Zaretskii wrote:
> FWIW, even the latest Studio 2012 doesn't yet support %z, according to
> this:
> 
>   http://msdn.microsoft.com/en-us/library/hf4y5e3w%28v=vs.110%29.aspx

I would prefer a runtime test as not everything may be documented but OK,
I see gnulib vasprintf check-in should go along the future %z check-in.



Thanks,
Jan

  reply	other threads:[~2012-10-01 17:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 17:32 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST Jan Kratochvil
2012-09-28 20:23 ` Sergio Durigan Junior
2012-09-29  6:08   ` Jan Kratochvil
2012-09-29 16:58 ` Jan Kratochvil
2012-09-30 16:56 ` Joel Brobecker
2012-10-01 16:48   ` Old OSes compatibility [Re: 64-bit (>4GB) inferior data types rules; TYPE_LENGTH: unsigned -> ULONGEST] Jan Kratochvil
2012-10-01 17:18     ` Pedro Alves
2012-10-01 17:38       ` Eli Zaretskii
2012-10-01 18:01         ` Pedro Alves
2012-10-01 19:14           ` Eli Zaretskii
2012-10-01 17:32     ` Eli Zaretskii
2012-10-01 17:55       ` Jan Kratochvil [this message]
2012-10-01 17:57         ` Joel Brobecker
2012-10-01 18:08           ` Jan Kratochvil
2012-10-01 18:13             ` Joel Brobecker
2012-10-01 18:29               ` Jan Kratochvil

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=20121001175455.GA3955@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=siddhesh@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).