public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/100269] New: [12 Regression] i686 biarch compiler fails for Darwin after r12-36. Date: Mon, 26 Apr 2021 14:51:46 +0000 [thread overview] Message-ID: <bug-100269-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100269 Bug ID: 100269 Summary: [12 Regression] i686 biarch compiler fails for Darwin after r12-36. Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: iains at gcc dot gnu.org Target Milestone: --- With the fix at r12-50-ga44895ce7ffbc26b4d765c40b5b346f8c9a9b762 applied, bootstrap still fails for a 32b host with a 64b multilib. $ ./gcc/xgcc -Bgcc -E -dM -m64 -xc /dev/null cc1: sorry, unimplemented: 64-bit mode not compiled in this is coming from i386-options.c:2050+ if ((TARGET_64BIT_P (opts->x_ix86_isa_flags) != 0) != ((opts->x_ix86_isa_flags & OPTION_MASK_ISA_64BIT) != 0)) sorry ("%i-bit mode not compiled in", (opts->x_ix86_isa_flags & OPTION_MASK_ISA_64BIT) ? 64 : 32); unfortunately, it is not obvious to me what fix I need to make here.
next reply other threads:[~2021-04-26 14:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-26 14:51 iains at gcc dot gnu.org [this message] 2021-04-26 14:53 ` [Bug bootstrap/100269] " iains at gcc dot gnu.org 2021-04-27 7:09 ` [Bug target/100269] " rguenth at gcc dot gnu.org 2021-04-28 20:28 ` iains at gcc dot gnu.org 2021-07-04 19:39 ` cvs-commit at gcc dot gnu.org 2021-07-06 13:05 ` iains 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-100269-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).