public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/97618] undefined reference to LC11 building for target MinGW-w64 32-bit Date: Sun, 07 Feb 2021 13:50:26 +0000 [thread overview] Message-ID: <bug-97618-4-KuBqdbDT2T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97618-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97618 --- Comment #4 from Brecht Sanders <brechtsanders at users dot sourceforge.net> --- Found a smaller project to reproduce the issue with: building BLAKE3 v0.3.7 from https://github.com/BLAKE3-team/BLAKE3 also has the issue when building with GCC11 for 32-bit MinGW-w64. Here I noticed that compiling with -O0 works around the problem, so the issue must be in the compiler optimization for i686.
next prev parent reply other threads:[~2021-02-07 13:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-28 13:46 [Bug c/97618] New: " brechtsanders at users dot sourceforge.net 2020-10-28 14:17 ` [Bug c/97618] " brechtsanders at users dot sourceforge.net 2020-10-28 15:48 ` brechtsanders at users dot sourceforge.net 2021-02-07 12:21 ` brechtsanders at users dot sourceforge.net 2021-02-07 13:50 ` brechtsanders at users dot sourceforge.net [this message] 2021-03-05 12:44 ` brechtsanders at users dot sourceforge.net
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-97618-4-KuBqdbDT2T@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).