public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
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: Mon, 16 Dec 2002 12:46:00 -0000	[thread overview]
Message-ID: <20021216204603.29446.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/7872; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/7872: ICE on legal code, regression from 3.0 and 2.9*
Date: Mon, 16 Dec 2002 14:41:09 -0600 (CST)

 On Sat, 14 Dec 2002, Richard Zidlicky wrote:
 
 > 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.
 
 I've never done it, and would not know whether the results I get are right 
 or wrong. So I prefer to leave things like that to people who are more 
 familiar with that than me, and rather concentrate on further searching 
 the database for reports.
 
 
 > >         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.
 
 Try to find the maintainers of the code and ask them for their opinion, 
 possibly in private mail. Maybe that helps, I see too many bugs slipping 
 through the cracks. Otherwise you may also send the patch to the list, and 
 put a "Unreviewed patch" in the subject to indicate that this is a 
 long-pending matter.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-12-16 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 12:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14 12:56 Richard Zidlicky
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=20021216204603.29446.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).