public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@gcc.gnu.org
To: davem@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
jakub@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: target/6466: Sparc backend uses bad types for frame size calculation.
Date: Thu, 25 Apr 2002 19:37:00 -0000 [thread overview]
Message-ID: <20020426023659.7213.qmail@sources.redhat.com> (raw)
Synopsis: Sparc backend uses bad types for frame size calculation.
Responsible-Changed-From-To: unassigned->jakub
Responsible-Changed-By: davem
Responsible-Changed-When: Thu Apr 25 19:36:59 2002
Responsible-Changed-Why:
Jakub already has a half-completed patch to deal
with this problem post-3.1
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6466
next reply other threads:[~2002-04-26 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 19:37 davem [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 9:42 target/6466: [SPARC] " ehrhardt
2003-05-17 9:56 Dara Hazeghi
2002-04-25 19:36 target/6466: Sparc " davem
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=20020426023659.7213.qmail@sources.redhat.com \
--to=davem@gcc.gnu.org \
--cc=davem@redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=jakub@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).