public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: weigand@i1.informatik.uni-erlangen.de, gcc@gcc.gnu.org
Subject: Re: Regression due to tree loop opt / expand weirdness
Date: Wed, 06 Oct 2004 17:20:00 -0000	[thread overview]
Message-ID: <200410061657.SAA14194@faui1m.informatik.uni-erlangen.de> (raw)
In-Reply-To: <10410061645.AA13509@vlsi1.ultra.nyu.edu> from "Richard Kenner" at Oct 06, 2004 12:45:04 PM

Richard Kenner wrote:
> 
>     First of all, the above change is provably a no-op on ia64 since
>     the valid_pointer_mode implementation on ia64 is the default one,
>     which is exactly (mode != Pmode && mode != ptr_mode).
> 
> Please read what I wrote.  On some ia64 systems (e.g., VMS), Pmode and
> ptr_mode are both DImode but you need to support 32-bit pointers.  On
> those ia64 systems, target.valid_pointer_mode is overridden to allow both
> SImode and DImode.

I could not find any such ia64 system in current GCC CVS, are you talking
about an out-of-tree port?

In any case, as I said, s390x/TPF is in exactly this situation (Pmode ==
ptr_mode == DImode, valid_pointer_mode overridden to allow both SImode
and DImode); and this case is exactly the one that my patch fixes.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  weigand@informatik.uni-erlangen.de

  reply	other threads:[~2004-10-06 16:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 17:13 Richard Kenner
2004-10-06 17:20 ` Ulrich Weigand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06 20:06 Richard Kenner
2004-10-06 20:17 ` Ulrich Weigand
2004-10-06 18:18 Richard Kenner
2004-10-06 19:59 ` Ulrich Weigand
2004-10-06 13:12 Richard Kenner
2004-10-06 14:46 ` Ulrich Weigand
2004-10-06 12:56 Richard Kenner
2004-10-06 14:21 ` Ulrich Weigand
2004-10-03 22:21 Ulrich Weigand
2004-10-03 22:31 ` Richard Henderson
2004-10-03 22:38   ` Ulrich Weigand
2004-10-03 22:55     ` Richard Henderson
2004-10-03 23:15       ` Ulrich Weigand
2004-10-04  4:00         ` Richard Henderson
2004-10-04  7:28           ` Ulrich Weigand
2004-10-04  9:21             ` Eric Christopher
2004-10-04 13:17   ` Zdenek Dvorak
2004-10-04 13:24     ` Paolo Bonzini
2004-10-04 14:08       ` Zdenek Dvorak
2004-10-04 14:42         ` Paolo Bonzini
2004-10-04 14:46           ` Zdenek Dvorak

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=200410061657.SAA14194@faui1m.informatik.uni-erlangen.de \
    --to=weigand@i1.informatik.uni-erlangen.de \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).