public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110789] Internal Compiler Error: Illegal instruction Date: Wed, 26 Jul 2023 06:49:50 +0000 [thread overview] Message-ID: <bug-110789-4-SRYkW73mMD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110789-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110789 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- If you compile GMP (MPFR and MPC) as part of GCC build rather than seperately, the build will do the correct thing and not use the "native" options by default. You could also configure GMP using --target=none-linux-gnu --host=none-linux-gnu --build=none-linux-gnu to disable that similar thing (just as building GMP as part of GCC's build). From Makefile.def: host_modules= { module= gmp; lib_path=.libs; bootstrap=true; // Work around in-tree gmp configure bug with missing flex. extra_configure_flags='--disable-shared LEX="touch lex.yy.c" @host_libs_picflag@'; extra_make_flags='AM_CFLAGS="-DNO_ASM"'; no_install= true; // none-*-* disables asm optimizations, bootstrap-testing // the compiler more thoroughly. host="none-${host_vendor}-${host_os}"; // gmp's configure will complain if given anything // different from host for target. target="none-${host_vendor}-${host_os}"; };
next prev parent reply other threads:[~2023-07-26 6:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 8:47 [Bug c/110789] New: " pledr at gmx dot net 2023-07-24 8:55 ` [Bug c/110789] " pinskia at gcc dot gnu.org 2023-07-24 8:59 ` pledr at gmx dot net 2023-07-24 9:04 ` arsen at gcc dot gnu.org 2023-07-24 15:07 ` pledr at gmx dot net 2023-07-24 16:29 ` pledr at gmx dot net 2023-07-26 6:44 ` pledr at gmx dot net 2023-07-26 6:49 ` pinskia at gcc dot gnu.org [this message] 2023-07-27 1:30 ` xry111 at gcc dot gnu.org 2023-07-27 5:05 ` xry111 at gcc dot gnu.org 2023-07-27 5:09 ` xry111 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-110789-4-SRYkW73mMD@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).