public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: denisc@overta.ru, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
rth@gcc.gnu.org
Subject: Re: target/3037: ARM port: Wrong flow info after reload
Date: Mon, 11 Jun 2001 14:34:00 -0000 [thread overview]
Message-ID: <20010611213436.5043.qmail@sourceware.cygnus.com> (raw)
Synopsis: ARM port: Wrong flow info after reload
State-Changed-From-To: open->feedback
State-Changed-By: rth
State-Changed-When: Mon Jun 11 14:34:36 2001
State-Changed-Why:
Err, ok, yes, the interaction between the arm backend and flow
keeps registers live when they oughtn't be. That seems rather
minor though. Why is this pr marked "critical"? I'm presuming
based on "ice-on-legal-code" that this test case was supposed
to segfault or something, but as you didn't give compilation
flags I was forced to guess, and didn't come up with a
combination that dies.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3037&database=gcc
next reply other threads:[~2001-06-11 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 14:34 rth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 16:14 rodrigc
2001-06-11 14:17 rth
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=20010611213436.5043.qmail@sourceware.cygnus.com \
--to=rth@gcc.gnu.org \
--cc=denisc@overta.ru \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-prs@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).