public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot bonzini at lu dot unisi dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19528] [4.0 regression] missing ra.h
Date: Wed, 19 Jan 2005 12:55:00 -0000 [thread overview]
Message-ID: <20050119125510.11776.qmail@sourceware.org> (raw)
In-Reply-To: <20050119095203.19528.corsepiu@gcc.gnu.org>
------- Additional Comments From paolo dot bonzini at lu dot unisi dot ch 2005-01-19 12:55 -------
Subject: Re: [4.0 regression] missing ra.h
steven at gcc dot gnu dot org wrote:
> ------- Additional Comments From steven at gcc dot gnu dot org 2005-01-19 12:26 -------
> ...and remove the #include "ra.h" of course.
Doh. I'm sorry for the breakage, but why the heck does the SH back-end
have to include it?
Why does the SH back-end have to behave different from every other one?^A^K
Paolo
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19528
next prev parent reply other threads:[~2005-01-19 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 9:52 [Bug target/19528] New: " corsepiu at gcc dot gnu dot org
2005-01-19 12:22 ` [Bug target/19528] " steven at gcc dot gnu dot org
2005-01-19 12:26 ` steven at gcc dot gnu dot org
2005-01-19 12:55 ` paolo dot bonzini at lu dot unisi dot ch [this message]
2005-01-19 13:27 ` bonzini at gcc dot gnu dot org
2005-01-19 13:47 ` bonzini at gcc dot gnu dot org
2005-01-19 13:48 ` pinskia at gcc dot gnu dot org
2005-01-19 14:03 ` pinskia at gcc dot gnu dot org
2005-01-19 16:35 ` corsepiu at gcc dot gnu dot org
2005-01-19 19:00 ` steven at gcc dot gnu dot org
2005-01-21 17:34 ` mmitchel at gcc dot gnu dot org
2005-01-22 12:20 ` steven at gcc dot gnu dot org
2005-01-22 12:57 ` joel at gcc dot gnu dot org
2005-01-22 19:43 ` mark at codesourcery dot com
2005-01-24 16:22 ` pinskia at gcc dot gnu dot org
2005-04-20 2:03 ` 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=20050119125510.11776.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).