public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/109460] Build gcc for win32 failed in gcc13 master branch Date: Wed, 12 Apr 2023 11:37:30 +0000 [thread overview] Message-ID: <bug-109460-4-NqgWIvPYV1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109460-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> --- As I said on IRC, even GCC 4.8 passes -r through to linker invocation, but only since r9-2994 gcc -r acts effectively the same as -r -nostdlib, before that one had to use both options to avoid linking crt files, standard libraries and the like even during the relocatable link. An open question remains if mingw/cygwin supports other host compilers for stage1, like clang, icc, msvc and the like, and whether -r or -r -nostdlib works for those.
next prev parent reply other threads:[~2023-04-12 11:37 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-10 3:10 [Bug c/109460] New: " fanghuaqi at vip dot qq.com 2023-04-10 19:54 ` [Bug c/109460] " costas.argyris at gmail dot com 2023-04-10 20:41 ` ebotcazou at gcc dot gnu.org 2023-04-10 21:41 ` costas.argyris at gmail dot com 2023-04-10 22:07 ` ebotcazou at gcc dot gnu.org 2023-04-10 22:43 ` costas.argyris at gmail dot com 2023-04-11 1:45 ` fanghuaqi at vip dot qq.com 2023-04-11 8:54 ` costas.argyris at gmail dot com 2023-04-11 9:01 ` costas.argyris at gmail dot com 2023-04-11 9:15 ` fanghuaqi at vip dot qq.com 2023-04-11 10:12 ` costas.argyris at gmail dot com 2023-04-11 12:03 ` costas.argyris at gmail dot com 2023-04-12 4:11 ` [Bug bootstrap/109460] " fanghuaqi at vip dot qq.com 2023-04-12 4:13 ` fanghuaqi at vip dot qq.com 2023-04-12 6:54 ` costas.argyris at gmail dot com 2023-04-12 7:09 ` fanghuaqi at vip dot qq.com 2023-04-12 8:21 ` costas.argyris at gmail dot com 2023-04-12 9:32 ` fanghuaqi at vip dot qq.com 2023-04-12 10:00 ` costas.argyris at gmail dot com 2023-04-12 10:01 ` ebotcazou at gcc dot gnu.org 2023-04-12 10:04 ` ebotcazou at gcc dot gnu.org 2023-04-12 10:40 ` fanghuaqi at vip dot qq.com 2023-04-12 10:41 ` fanghuaqi at vip dot qq.com 2023-04-12 10:47 ` ebotcazou at gcc dot gnu.org 2023-04-12 11:17 ` costas.argyris at gmail dot com 2023-04-12 11:33 ` fanghuaqi at vip dot qq.com 2023-04-12 11:37 ` jakub at gcc dot gnu.org [this message] 2023-04-12 11:40 ` ebotcazou at gcc dot gnu.org 2023-04-12 11:58 ` costas.argyris at gmail dot com 2023-04-12 13:16 ` costas.argyris at gmail dot com 2023-04-12 14:41 ` burnus at gcc dot gnu.org 2023-04-12 14:45 ` costas.argyris at gmail dot com 2023-04-12 15:09 ` segher at gcc dot gnu.org 2023-04-12 15:17 ` segher at gcc dot gnu.org 2023-04-12 15:30 ` costas.argyris at gmail dot com 2023-04-13 3:09 ` fanghuaqi at vip dot qq.com 2023-04-13 9:12 ` costas.argyris at gmail 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-109460-4-NqgWIvPYV1@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).