public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: martin@bruli.net To: gcc-gnats@gcc.gnu.org Cc: martin@bruli.net Subject: optimization/8873: Optimization on alpha (ev5) Date: Sun, 08 Dec 2002 07:16:00 -0000 [thread overview] Message-ID: <200212081514.gB8FElh5002912@alps.bruli.net> (raw) >Number: 8873 >Category: optimization >Synopsis: Optimization on alpha (ev5) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun Dec 08 07:16:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Martin Brulisauer >Release: 3.2.1 >Organization: MBE >Environment: System: Linux alps 2.4.19 #3 Mon Nov 25 10:57:02 MET 2002 alpha unknown Architecture: alpha host: alphaev5-bruli-linux-gnu build: alphaev5-bruli-linux-gnu target: alphaev5-bruli-linux-gnu configured with: ./configure --prefix=/usr --exec-prefix=/usr --host=alphaev5-bruli-linux --enable-threads=posix --enable-shared --disable-static >Description: Compiling glibc-2.3.1 using -mcpu=ev5 generates code that does not run correctly on alpha/ev5. Compiling ssh-3.1 using -mcpu=ev5 generates code that does not run at all. >How-To-Repeat: Compile the source using -mcpu=ev5 on a ev5 machine and try to run this code. >Fix: Using -mcpu=ev4 generates runnable code. (The advantages of the ev5 over the ev4 is lost). >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-08 15:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-08 7:16 martin [this message] 2002-12-08 15:46 Falk Hueffner 2003-02-18 13:40 ebotcazou 2003-02-18 17:16 martin 2003-02-19 9:06 Eric Botcazou 2003-03-07 9:36 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=200212081514.gB8FElh5002912@alps.bruli.net \ --to=martin@bruli.net \ --cc=gcc-gnats@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: linkBe 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).