public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc@gcc.gnu.org, dave@hiauly1.hia.nrc.ca
Subject: Re: Vector modes under hppa64-hpu
Date: Thu, 25 Jul 2002 02:36:00 -0000	[thread overview]
Message-ID: <20020724152619.A21800@redhat.com> (raw)
In-Reply-To: <200207242125.OAA17485@hpsje.cup.hp.com>; from sje@cup.hp.com on Wed, Jul 24, 2002 at 02:25:03PM -0700

> I don't know if building a cross ia64-hpux will work or not, but a pa64
> version should at least build cc1.  These two platforms are behaving
> slightly differently for me.  I can make IA64 work at all optimization
> levels with the change that I included in my earlier mail
> (http://gcc.gnu.org/ml/gcc/2002-07/msg01148.html) but PA64 will only
> work at -O0 with that change, -O1/-O2/etc still fail with the
> simplify_gen_subreg message.

flamingo:~/build/pa64/gcc$ cat a.c
typedef int v2si __attribute__ ((mode(V2SI)));
typedef unsigned di __attribute__ ((mode(DI)));
void foo(unsigned long);
void bar() {
            v2si x = { 1, 2 };
                foo((di) x);
}

flamingo:~/build/pa64/gcc$ ./cc1 a.c -O0 -quiet
flamingo:~/build/pa64/gcc$ ./cc1 a.c -O -quiet
flamingo:~/build/pa64/gcc$ ./cc1 a.c -O2 -quiet

no problem here.  --target=hppa64-linux

I tried --target=hppa64-hpux but configure dies with

*** Configuration hppa64-hp-hpux not supported
Configure in /home/aldyh/build/pa64/gcc failed, exiting.

If you can get me a cross target triplet combo that'll build me a
cross ./cc1... I'll [try to] fix your problem ;-).

Aldy

  reply	other threads:[~2002-07-24 22:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  2:02 Steve Ellcey
2002-07-25  2:36 ` Aldy Hernandez [this message]
2002-07-25  2:54   ` John David Anglin
2002-07-25  2:56     ` Aldy Hernandez
2002-07-25 11:22       ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 22:07 Joern Rennecke
2002-07-26  1:56 ` John David Anglin
2002-07-25 20:57 Joern Rennecke
2002-07-25 21:21 ` Aldy Hernandez
2002-07-26  3:20   ` Joern Rennecke
2002-07-27  5:54     ` John David Anglin
2002-07-27  7:35 ` Aldy Hernandez
2002-07-28  9:52   ` Richard Henderson
2002-07-25 15:19 Steve Ellcey
2002-07-25 15:28 ` Aldy Hernandez
2002-07-25 11:40 Steve Ellcey
2002-07-25 14:52 ` Aldy Hernandez
2002-07-25  3:53 Steve Ellcey
2002-07-25  0:09 Steve Ellcey
2002-07-25  1:01 ` Aldy Hernandez
2002-07-24 17:42 Steve Ellcey
2002-07-24 18:12 ` Aldy Hernandez
2002-07-24 15:22 Steve Ellcey
2002-07-24 16:30 ` Aldy Hernandez
2002-07-24 14:11 Steve Ellcey
2002-07-14 23:15 Aldy Hernandez

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=20020724152619.A21800@redhat.com \
    --to=aldyh@redhat.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=sje@cup.hp.com \
    /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).