public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7872: ICE on legal code, regression from 3.0 and 2.9*
Date: Sat, 14 Dec 2002 12:56:00 -0000 [thread overview]
Message-ID: <20021214205602.9547.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/7872; it has been noted by GNATS.
From: Richard Zidlicky <rz@linux-m68k.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: c/7872: ICE on legal code, regression from 3.0 and 2.9*
Date: Sat, 14 Dec 2002 20:38:21 +0100
On Wed, Nov 27, 2002 at 03:45:46PM -0000, bangerth@dealii.org wrote:
> Synopsis: ICE on legal code, regression from 3.0 and 2.9*
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bangerth
> State-Changed-When: Wed Nov 27 07:45:44 2002
> State-Changed-Why:
> Richard, same here: I don't have an m68k so cannot check your problem.
you can, the bugreport should have enough information to configure the
cross-compiler and all the necessary input to test the problem on any
architecture.
> What happened to the patch you appended? I does not seem
> to have been applied...
Unfortunately untill now I have seen absolutely no response to this
bugreport, thanks for looking at it.
Quite possible my solution is not the correct or best one, I noticed
the problem would also go away if m68k had CLASS_CANNOT_CHANGE_MODE
defined. However the gcc docs describe this as something that should
affect floating point only so I am not sure about this.
Richard
next reply other threads:[~2002-12-14 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 12:56 Richard Zidlicky [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 12:46 Wolfgang Bangerth
2002-09-09 14:36 Richard Zidlicky
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=20021214205602.9547.qmail@sources.redhat.com \
--to=rz@linux-m68k.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).