public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bunk at stusta dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102602] New: [10/11/12 Regression] 32bit mips: Error: branch out of range Date: Tue, 05 Oct 2021 08:13:24 +0000 [thread overview] Message-ID: <bug-102602-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102602 Bug ID: 102602 Summary: [10/11/12 Regression] 32bit mips: Error: branch out of range Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bunk at stusta dot de Target Milestone: --- Created attachment 51552 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51552&action=edit Preprocessed sources With a command like /usr/lib/gcc/mipsel-linux-gnu/10/cc1plus -fpreprocessed Options.ii -mel -quiet -dumpbase Options.ii -march=mips32r2 -auxbase Options -O2 -version -o /tmp/cccmq2Yu.s the attached file from a failed build of https://tracker.debian.org/pkg/kstars generates code the assembler rejects. $ g++-10 -c -O2 Options.ii /tmp/ccecXwRM.s: Assembler messages: /tmp/ccecXwRM.s:4908: Error: branch out of range /tmp/ccecXwRM.s:54845: Error: branch out of range /tmp/ccecXwRM.s:54868: Error: branch out of range $ For working and known broken gcc versions, Debian revisions and date they were taken from the upstream branch are: Working: 10.2.1-6 (git 20210110 from the gcc-10 branch) Broken: 10.3.0-11 (git 20210918 from the gcc-10 branch) 11.2.0-8 (git 20210924 from the gcc-11 branch) 20210909-1 (git 20210918 from master)
next reply other threads:[~2021-10-05 8:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 8:13 bunk at stusta dot de [this message] 2021-10-05 8:14 ` [Bug target/102602] " bunk at stusta dot de 2021-10-05 12:20 ` rguenth at gcc dot gnu.org 2021-10-17 20:23 ` [Bug target/102602] " pinskia at gcc dot gnu.org 2021-10-17 20:32 ` pinskia at gcc dot gnu.org
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=bug-102602-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).