public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giulio.benetti at benettiengineering dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99410] New: Nios II Error: branch offset out of range Date: Fri, 05 Mar 2021 14:30:34 +0000 [thread overview] Message-ID: <bug-99410-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99410 Bug ID: 99410 Summary: Nios II Error: branch offset out of range Product: gcc Version: 7.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: giulio.benetti at benettiengineering dot com Target Milestone: --- When building git package on Buildroot gcc throws: ''' [ 98%] Building C object src/CMakeFiles/bellesip.dir/antlr3c/src/antlr3treeparser.c.o /tmp/ccDtjRfo.s: Assembler messages: /tmp/ccDtjRfo.s:210798: Error: branch offset out of range /tmp/ccDtjRfo.s: Fatal error: branch relaxation failed ''' To reproduce it: # git clone git://git.busybox.net/buildroot # wget https://git.busybox.net/buildroot-test/tree/utils/br-reproduce-build - modify BASE_GIT=... with your buildroot path in br-reproduce-build then: # chmod a+x br-reproduce-build # ./br-reproduce-build 71f26fd81db8e9b19b3f18f3f3cefd9c768f094f The only way I've found to build correctly is to turn off optimization overriding CFLAGS with -O0.
next reply other threads:[~2021-03-05 14:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 14:30 giulio.benetti at benettiengineering dot com [this message] 2021-03-05 18:47 ` [Bug target/99410] " pinskia at gcc dot gnu.org 2021-03-05 19:03 ` giulio.benetti at benettiengineering dot com 2021-03-05 19:28 ` giulio.benetti at benettiengineering dot com 2021-08-20 23:13 ` giulio.benetti at benettiengineering dot com 2021-08-20 23:22 ` giulio.benetti at benettiengineering dot com 2021-08-20 23:28 ` giulio.benetti at benettiengineering dot com 2021-08-20 23:29 ` giulio.benetti at benettiengineering dot com 2021-08-21 21:12 ` giulio.benetti at benettiengineering dot com 2022-07-29 16:17 ` giulio.benetti at benettiengineering dot com
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-99410-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).