public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: thorpej@wasabisystems.com To: gcc-gnats@gcc.gnu.org Subject: target/6603: sh-elf fails to build libgcc Date: Tue, 07 May 2002 23:06:00 -0000 [thread overview] Message-ID: <20020508060025.29742.qmail@sources.redhat.com> (raw) >Number: 6603 >Category: target >Synopsis: sh-elf fails to build libgcc >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue May 07 23:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jason R Thorpe >Release: gcc version 3.2 20020507 (experimental) >Organization: >Environment: i386-netbsdelf host and sh-elf target >Description: Building a sh-elf compiler fails while building __muldi3 for libgcc: ../../../gcc/gcc/libgcc2.c: In function `__muldi3': ../../../gcc/gcc/libgcc2.c:367: RTL flag check: access macro used with unexpected rtx code `jump_insn' in dbr_schedule, at reorg.c:3631 A similar failure occurs while building the same function for with the sh-netbsdelf configuration I posted some time ago (problems in updating this configuration prompted this report). >How-To-Repeat: Attempt to build a sh-elf compiler. >Fix: The function can be compiled with -O0. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-05-08 6:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020508060025.29742.qmail@sources.redhat.com \ --to=thorpej@wasabisystems.com \ --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).