From: Michael Snyder <msnyder@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com, fnasser@redhat.com
Subject: Re: [RFA] Add "long long" tests to whatis.exp
Date: Fri, 21 Sep 2001 11:15:00 -0000 [thread overview]
Message-ID: <3BAB83C9.F6D224E4@cygnus.com> (raw)
In-Reply-To: <7458-Fri21Sep2001101238+0300-eliz@is.elta.co.il>
Eli Zaretskii wrote:
>
> > Date: Thu, 20 Sep 2001 14:36:29 -0700
> > From: Michael Snyder <msnyder@cygnus.com>
> >
> > 2001-09-20 Michael Snyder <msnyder@redhat.com>
> >
> > * gdb.base/whatis.exp: Add tests for long long.
>
> Are we sure all supported compilers have long long? If not, these
> tests will fail to compile when the test suite is run.
There are at least three other test files in gdb.base that
unconditionally declare a long long:
long_long.c
varargs.c
return2.c
I haven't heard anything about them failing to compile
in some environments, but if they do, then we need a
general mechanism for dealing with the problem.
Michael
prev parent reply other threads:[~2001-09-21 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 14:36 Michael Snyder
[not found] ` <7458-Fri21Sep2001101238+0300-eliz@is.elta.co.il>
2001-09-21 11:15 ` Michael Snyder [this message]
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=3BAB83C9.F6D224E4@cygnus.com \
--to=msnyder@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.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