public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Hartmut Penner" <HPENNER@de.ibm.com>
To: uweigand@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6305: c++ gets ICE in reload_cse_simplify_operands
Date: Tue, 16 Apr 2002 03:06:00 -0000	[thread overview]
Message-ID: <20020416100604.11385.qmail@sources.redhat.com> (raw)

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

From: "Hartmut Penner" <HPENNER@de.ibm.com>
To: uweigand@gcc.gnu.org, "Hartmut Penner" <HPENNER@de.ibm.com>,
        "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>, aj@suse.de,
        gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
        pthomas@suse.de, uweigand@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/6305: c++ gets ICE in reload_cse_simplify_operands
Date: Tue, 16 Apr 2002 12:00:39 +0200

 Uli,
       ich habe mal ein wenig reingeschaut.
 Die Function find_reg gibt fuer ein SI Pseudo das Floating point regist=
 er
 %f4 zurueck und das Unheil nimmt
 seinen Lauf.  Das wiederum kommt daher, das HARD_REGNO_MODE_OK fuer die=
  reg
 18 und SImode ein true
 zurueckgibt. Du hast das am 16-12-2001 eingefuehrt mit der Begruendung,=
 
 'Allow SI und DI in Floating Point register'.
 Das hatte bestimmt gewichtige Gruende, ruf mich doch mal an, wenn Du da=
 
 bist.
 
 Bzgl 6306 (mulsidi3) habe ich local einen fix ausprobiert, ich lasse
 einfach ein zero_extendsidi2 for der mul3264 machen,
 das ist zwar nicht der beste code (unnoetige lhi even_reg, 0) aber trap=
 pt
 nicht.
 
 Mit freundlichem Gru=DF / Best regards,
 
 Hartmut Penner
 GCC for S/390 Development
 
 Internet Mail Address : hpenner@de.ibm.com
 
 Tel: (49)-7031-16-4364=
 
 


             reply	other threads:[~2002-04-16 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16  3:06 Hartmut Penner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-17  5:33 uweigand
2002-04-15 13:10 uweigand
2002-04-15  5:06 pthomas

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=20020416100604.11385.qmail@sources.redhat.com \
    --to=hpenner@de.ibm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=uweigand@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).