public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8873: Optimization on alpha (ev5)
Date: Sun, 08 Dec 2002 15:46:00 -0000 [thread overview]
Message-ID: <20021208234602.4688.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/8873; it has been noted by GNATS.
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: martin@bruli.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/8873: Optimization on alpha (ev5)
Date: 09 Dec 2002 00:40:54 +0100
martin@bruli.net writes:
> Compiling glibc-2.3.1 using -mcpu=ev5 generates code that does
> not run correctly on alpha/ev5.
In which way?
> Compiling ssh-3.1 using -mcpu=ev5 generates code that does not
> run at all.
Could you be more specific? Does it crash? With what signal?
--
Falk
next reply other threads:[~2002-12-08 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 15:46 Falk Hueffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 9:36 martin
2003-02-19 9:06 Eric Botcazou
2003-02-18 17:16 martin
2003-02-18 13:40 ebotcazou
2002-12-08 7:16 martin
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=20021208234602.4688.qmail@sources.redhat.com \
--to=falk.hueffner@student.uni-tuebingen.de \
--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).