public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason.vas.dias at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/54179] please split insn-emit.c ! Date: Sun, 05 Aug 2012 20:58:00 -0000 [thread overview] Message-ID: <bug-54179-4-KsUaiYpnF0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54179-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179 --- Comment #26 from Jason Vas Dias <jason.vas.dias at gmail dot com> 2012-08-05 20:57:59 UTC --- Well, when I read on the documentation page http://gcc.gnu.org/install/configure.html --enable-build-with-cxx Build GCC using a C++ compiler rather than a C compiler. This is an experimental option which may become the default in a later release. --enable-bootstrap In special cases, you may want to perform a 3-stage build even if the target and host triplets are different. This is possible when the host can run code compiled for the target (e.g. host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do this you have to configure explicitly with --enable-bootstrap. --enable-checking --enable-checking=list When you specify this option, the compiler is built to perform internal consistency checks of the requested complexity. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building the compiler with GCC. This is `yes' by default when building from SVN or snapshots, but `release' for releases. The default for building the stage1 compiler is `yes'. More control over the checks may be had by specifying list. The categories of checks available are `yes' (most common checks `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at all), `all' (all but `valgrind'), `release' (cheapest checks `assert,runtime') or `none' (same as `no'). Individual checks can be enabled with these flags `assert', `df', `fold', `gc', `gcac' `misc', `rtl', `rtlflag', `runtime', `tree', and `valgrind'. The `valgrind' check requires the external valgrind simulator, available from http://valgrind.org/. The `df', `rtl', `gcac' and `valgrind' checks are very expensive. To disable all checking, `--disable-checking' or `--enable-checking=none' must be explicitly requested. Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. Where does it say I cannot build "C" and not "C++" without specifying --enable-languages=c --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-stage1-languages=c which is in fact the case ? Where does it say that users should never use "--enable-checking=all" with "--enable-bootstrap" ? And what has any of this to do with the simple question posed in the title of this bug report : why can't insn-emit.c be split ?
next prev parent reply other threads:[~2012-08-05 20:58 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-05 11:05 [Bug c/54179] New: " jason.vas.dias at gmail dot com 2012-08-05 11:11 ` [Bug c/54179] " jason.vas.dias at gmail dot com 2012-08-05 11:22 ` wbrana at gmail dot com 2012-08-05 11:36 ` jason.vas.dias at gmail dot com 2012-08-05 11:43 ` jason.vas.dias at gmail dot com 2012-08-05 12:01 ` wbrana at gmail dot com 2012-08-05 12:04 ` steven at gcc dot gnu.org 2012-08-05 12:21 ` jason.vas.dias at gmail dot com 2012-08-05 12:28 ` wbrana at gmail dot com 2012-08-05 12:34 ` steven at gcc dot gnu.org 2012-08-05 12:37 ` steven at gcc dot gnu.org 2012-08-05 13:16 ` jason.vas.dias at gmail dot com 2012-08-05 13:31 ` wbrana at gmail dot com 2012-08-05 13:43 ` jason.vas.dias at gmail dot com 2012-08-05 13:46 ` jason.vas.dias at gmail dot com 2012-08-05 13:51 ` jason.vas.dias at gmail dot com 2012-08-05 13:54 ` steven at gcc dot gnu.org 2012-08-05 13:55 ` steven at gcc dot gnu.org 2012-08-05 14:12 ` wbrana at gmail dot com 2012-08-05 14:13 ` schwab@linux-m68k.org 2012-08-05 18:10 ` jason.vas.dias at gmail dot com 2012-08-05 18:39 ` steven at gcc dot gnu.org 2012-08-05 19:49 ` jason.vas.dias at gmail dot com 2012-08-05 19:52 ` jason.vas.dias at gmail dot com 2012-08-05 20:10 ` jason.vas.dias at gmail dot com 2012-08-05 20:17 ` steven at gcc dot gnu.org 2012-08-05 20:58 ` jason.vas.dias at gmail dot com [this message] 2012-08-05 21:05 ` steven at gcc dot gnu.org 2012-08-06 8:43 ` rguenth at gcc dot gnu.org 2012-08-06 9:11 ` steven at gcc dot gnu.org 2012-08-06 10:49 ` steven at gcc dot gnu.org 2023-07-06 10:49 ` mmokrejs at gmail dot com 2023-07-07 11:29 ` sjames at gcc dot gnu.org 2023-07-07 11:39 ` [Bug bootstrap/54179] " tnfchris at gcc dot gnu.org 2023-07-07 12:47 ` mmokrejs at gmail dot com 2023-10-31 12:48 ` sjames at gcc dot gnu.org 2023-11-13 13:07 ` brjd_epdjq36 at kygur dot com 2023-11-13 15:03 ` xry111 at gcc dot gnu.org 2023-11-13 15:12 ` brjd_epdjq36 at kygur dot com 2024-05-11 12:08 ` brjd_epdjq36 at kygur dot com 2024-05-12 4:29 ` sjames at gcc dot gnu.org 2024-05-12 10:19 ` brjd_epdjq36 at kygur 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-54179-4-KsUaiYpnF0@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).