public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org
To: David.Billinghurst@riotinto.com, gcc-bugs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk,
	nobody@gcc.gnu.org, zack@gcc.gnu.org
Subject: Re: c/4939: [cygwin] Failure of test gcc.dg/c99-intconst-1.c
Date: Tue, 20 Nov 2001 00:06:00 -0000	[thread overview]
Message-ID: <20011124110040.17153.qmail@sourceware.cygnus.com> (raw)

Synopsis: [cygwin] Failure of test gcc.dg/c99-intconst-1.c

Responsible-Changed-From-To: unassigned->zack
Responsible-Changed-By: jsm28
Responsible-Changed-When: Sat Nov 24 03:00:39 2001
Responsible-Changed-Why:
    The testcase failures are expected until Zack's patch is in.
    The deficiencies in Cygwin's <limits.h> - if GCC needs to
    use that rather than its own functional <limits.h> - are
    for the Cygwin maintainers to deal with, though
    fixincludes perhaps ought to fix the problems on existing
    versions of Cygwin with deficient headers.
State-Changed-From-To: open->analyzed
State-Changed-By: jsm28
State-Changed-When: Sat Nov 24 03:00:39 2001
State-Changed-Why:
    The testcase fails (depending on architecture).  This is expected.
    Zack asked me to write the testcases; having done so I added them.
    http://gcc.gnu.org/ml/gcc-patches/2001-08/msg01411.html
    http://gcc.gnu.org/ml/gcc-patches/2001-11/msg01370.html

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4939&database=gcc


             reply	other threads:[~2001-11-24 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20  0:06 jsm28 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-09  6:09 neil
2001-11-20  0:36 jsm28
2001-11-19 21:36 David.Billinghurst

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=20011124110040.17153.qmail@sourceware.cygnus.com \
    --to=jsm28@gcc.gnu.org \
    --cc=David.Billinghurst@riotinto.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=nobody@gcc.gnu.org \
    --cc=zack@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).