public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Dave Korn" <davek-ml@ntlworld.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2371: Hang with long long function argument.
Date: Sat, 31 Mar 2001 21:56:00 -0000 [thread overview]
Message-ID: <20010401055601.14266.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/2371; it has been noted by GNATS.
From: "Dave Korn" <davek-ml@ntlworld.com>
To: <snowball3@bigfoot.com>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: c/2371: Hang with long long function argument.
Date: Sun, 1 Apr 2001 06:45:55 +0100
----- Original Message -----
From: <snowball3@bigfoot.com>
To: <gcc-gnats@gcc.gnu.org>
Sent: Saturday, March 24, 2001 4:53 AM
Subject: c/2371: Hang with long long function argument.
> >Description:
> It seems that code generated for handling variables of
> type 'long long' is incorrect. The sample program when
> run hangs. Changing the type to 'long' allows the program
> to exit normally.
> >How-To-Repeat:
> # 1 "longlong.c"
> int long_long_test( long long x)
> {
> do
> {
> x =- 1;
> } while (x);
It seems that you meant to say x-=1 there. Otherwise looping forever is
the expected behaviour. I've tested your code with both longs and long
longs, and both with and without your bugfix. Both the bugged versions
looped forever and both the fixed versions exit almost instantly. Are you
sure you didn't fix the bug at the same time as you changed from long longs
to plain longs?
DaveK
next reply other threads:[~2001-03-31 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 21:56 Dave Korn [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 7:16 Mark E.
2001-03-23 19:56 snowball3
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=20010401055601.14266.qmail@sourceware.cygnus.com \
--to=davek-ml@ntlworld.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).