public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19698] [3.3/3.4/4.0 regression] Infinite loop in update_life_info
Date: Sun, 30 Jan 2005 23:00:00 -0000 [thread overview]
Message-ID: <20050130230053.31432.qmail@sourceware.org> (raw)
In-Reply-To: <20050129191719.19698.schwab@suse.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-30 23:00 -------
(In reply to comment #7)
> Triggered by this change:
I think that only added the pure attribute on __builtin_cos.
You might want to try this testcase which shows the problem without a builtin:
float f(float) __attribute__((__pure__));
void FFT(int NumSamples, float *RealOut, float ar1)
{
int i, j, n;
int BlockSize, BlockEnd;
if (NumSamples <= 1)
return;
i = 0;
L1:
RealOut[i] = (RealOut == 0) ? 0.0 : RealOut[i];
i++;
if (NumSamples <= i) goto L1;
BlockEnd = 1;
for (BlockSize = 2; BlockSize <= NumSamples; BlockSize *=2)
{
float cm1 = f(-1.0);
for (i = 0; i < NumSamples; i += BlockSize)
for (j = i, n = 0; n < BlockEnd; j++, n++)
RealOut[j] = cm1 * ar1;
BlockEnd = BlockSize;
}
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19698
next prev parent reply other threads:[~2005-01-30 23:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 19:17 [Bug middle-end/19698] New: [4.0 " schwab at suse dot de
2005-01-29 19:18 ` [Bug middle-end/19698] " schwab at suse dot de
2005-01-29 19:24 ` pinskia at gcc dot gnu dot org
2005-01-30 2:34 ` schwab at suse dot de
2005-01-30 2:43 ` pinskia at gcc dot gnu dot org
2005-01-30 3:30 ` pinskia at gcc dot gnu dot org
2005-01-30 4:09 ` pinskia at gcc dot gnu dot org
2005-01-30 13:47 ` [Bug middle-end/19698] [3.3/3.4/4.0 " schwab at suse dot de
2005-01-30 13:59 ` pinskia at gcc dot gnu dot org
2005-01-30 22:25 ` schwab at suse dot de
2005-01-30 23:00 ` pinskia at gcc dot gnu dot org [this message]
2005-01-30 23:07 ` pinskia at gcc dot gnu dot org
2005-01-31 0:13 ` [Bug middle-end/19698] " schwab at suse dot de
2005-01-31 0:15 ` [Bug middle-end/19698] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-31 0:19 ` schwab at suse dot de
2005-01-31 7:22 ` ebotcazou at gcc dot gnu dot org
2005-01-31 7:33 ` steven at gcc dot gnu dot org
2005-01-31 7:38 ` ebotcazou at gcc dot gnu dot org
2005-02-12 20:39 ` steven at gcc dot gnu dot org
2005-02-14 10:01 ` steven at gcc dot gnu dot org
2005-02-14 11:19 ` steven at gcc dot gnu dot org
2005-02-20 17:23 ` cvs-commit at gcc dot gnu dot org
2005-02-20 17:36 ` steven at gcc dot gnu dot org
2005-02-20 19:00 ` pinskia at gcc dot gnu dot org
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=20050130230053.31432.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).