public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ross.alexander@uk.neceur.com
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/4844: Code generation bug for hppa64
Date: Tue, 20 Nov 2001 23:05:00 -0000 [thread overview]
Message-ID: <20011126132603.26536.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/4844; it has been noted by GNATS.
From: ross.alexander@uk.neceur.com
To: gcc-gnats@gcc.gnu.org
Cc: law@cygnus.com
Subject: Re: c/4844: Code generation bug for hppa64
Date: Mon, 26 Nov 2001 13:18:40 +0000
To all concerned,
After some investigation I have tracked the problem down to
expr.c. The statement
b.neg = !b.neg;
Somewhere this generates a tree EQ_EXPR. In expand_expr
the do_store_flag (line 7896) fails and the code falls through to
TRUTH_ANDIF_EXPR which as the line
if (target)
emit_clr_insn(target);
Unfortunately as the target is also the RHS on the expr it clears
the value before it gets a chance to all emit_0_1_insn.
I don't really have a good enough understanding of what is going
on to do anything more about this.
Any help would be most appriciated.
Many thanks
Ross
---------------------------------------------------------------------------------
Ross Alexander "He knows no more about his
MIS - NEC Europe Limited destiny than a tea leaf knows
Work ph: +44 20 8752 3394 the history of East India Company"
gcc-gnats@gcc
.gnu.org To: Ross Alexander <ross.alexander@uk.neceur.com>
cc:
09/11/01 Subject: Re: c/4844: Code generation bug for hppa64
17:56
Please
respond to
gcc-gnats;
Please
respond to
nobody
Thank you very much for your problem report.
It has the internal identification `c/4844'.
The individual assigned to look at your
report is: unassigned.
>Category: c
>Responsible: unassigned
>Synopsis: Code generation bug for hppa64
>Arrival-Date: Fri Nov 09 09:56:01 PST 2001
reply other threads:[~2001-11-26 13:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011126132603.26536.qmail@sourceware.cygnus.com \
--to=ross.alexander@uk.neceur.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).