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 target/93847] Nios II ICE Date: Fri, 05 Mar 2021 16:50:54 +0000 [thread overview] Message-ID: <bug-93847-4-60CtW5nZLd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93847-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93847 --- Comment #3 from Giulio Benetti <giulio.benetti at benettiengineering dot com> --- Hello, can you point me a way to provide the test cases you need? Also, now the bug shows using Buildroot but while compiling a toolchain from scratch, instructions follow: 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 24c0a6ca3b272711a1e6ceaa033925182d0d49c4 To reissue building: # cd 24c0a6ca3b272711a1e6ceaa033925182d0d49c4/output # make asterisk-dirclean asterisk If this is not enough, can you please me point the rules to create what you need? Thanks in advance!
next prev parent reply other threads:[~2021-03-05 16:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93847-4@http.gcc.gnu.org/bugzilla/> 2020-04-15 1:46 ` sandra at gcc dot gnu.org 2021-03-05 16:50 ` giulio.benetti at benettiengineering dot com [this message] 2021-08-21 22:01 ` giulio.benetti at benettiengineering dot com 2021-08-21 22:02 ` 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-93847-4-60CtW5nZLd@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).