public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/6833: gcse generates wrong code with regard to global register variables
Date: Mon, 17 Mar 2003 10:16:00 -0000 [thread overview]
Message-ID: <20030317101601.4245.qmail@sources.redhat.com> (raw)
The following reply was made to PR middle-end/6833; it has been noted by GNATS.
From: Bruno Haible <bruno@clisp.org>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: middle-end/6833: gcse generates wrong code with regard to global register variables
Date: Mon, 17 Mar 2003 11:10:38 +0100 (CET)
Wolfgang writes:
> Synopsis: gcse generates wrong code with regard to global register variables
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bangerth
> State-Changed-When: Sat Mar 15 03:21:07 2003
> State-Changed-Why:
> Bruno, I don't have 3.1 around any more, but I can't
> reproduce this with 3.2 and 3.2.2.
Still, could you add my testcase to the testsuite? Global register
variables are not used by many programs, but GNU clisp relies on them
very much. I'd like to not see this bug appear again.
Bruno
next reply other threads:[~2003-03-17 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 10:16 Bruno Haible [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-23 12:56 Bruno Haible
2003-03-20 1:06 Wolfgang Bangerth
2003-03-20 1:04 bangerth
2003-03-17 23:36 Wolfgang Bangerth
2003-03-15 3:21 bangerth
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=20030317101601.4245.qmail@sources.redhat.com \
--to=bruno@clisp.org \
--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).