public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: L-marks@nwu.edu To: gcc-gnats@gcc.gnu.org Subject: c/7047: -march=2.0 often fails Date: Sun, 16 Jun 2002 06:56:00 -0000 [thread overview] Message-ID: <20020616133812.31533.qmail@sources.redhat.com> (raw) >Number: 7047 >Category: c >Synopsis: -march=2.0 often fails >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Jun 16 06:46:27 PDT 2002 >Closed-Date: >Last-Modified: >Originator: L. D. Marks >Release: gcc 3.1 >Organization: >Environment: HPUX >Description: The PA 2.0 option -march=2.0 often fails, even with gcc code itself../../gcc-3.1/gcc/sched-rgn.c: In function `init_ready_list': Example of output ../../gcc-3.1/gcc/sched-rgn.c:2569: insn does not satisfy its constraints: (insn 1090 1088 106 (set (reg:SI 69 %fr22R) (mem/f:SI (lo_sum:SI (reg/f:SI 5 %r5 [142]) (symbol_ref:SI ("rgn_nr_edges"))) [3 rgn_nr_edges+0 S4 A32])) 68 {*pa.md:2088} (nil) (nil)) ../../gcc-3.1/gcc/sched-rgn.c:2569: Internal compiler error in reload_cse_simplify_operands, at reload1.c:8368 >How-To-Repeat: In stage 2 (or 1 or other code) stage2/xgcc -Bstage2/ -B/usr/local/hppa2.0-hp-hpux10.20/bin/ -c -DIN_GCC -O3 -fomit-frame-pointer -march=2.0 -mlinker-opt -D_HPUX_SOURCE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc-3.1/gcc -I../../gcc-3.1/gcc/. -I../../gcc-3.1/gcc/config -I../../gcc-3.1/gcc/../include ../../gcc-3.1/gcc/sched-rgn.c -o sched-rgn.o >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-16 13:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-16 6:56 L-marks [this message] 2002-06-16 11:56 law 2002-06-16 13:46 L. D. Marks 2002-06-16 23:07 law
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=20020616133812.31533.qmail@sources.redhat.com \ --to=l-marks@nwu.edu \ --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).