public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jay.krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46597] configure -enable-checking=... -enable-build-with-cxx and bootstrap is g++ 3.3 hit minor problem
Date: Tue, 28 Dec 2010 13:50:00 -0000	[thread overview]
Message-ID: <bug-46597-4-SPuG1e3o2f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46597-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46597

--- Comment #1 from Jay <jay.krell at cornell dot edu> 2010-12-28 13:50:06 UTC ---
I put #define ENABLE_CHECKING_GCC_VERSION ((GCC_VERSION > 3003) ||
(!defined(__cplusplus) && (GCC_VERSION > 2007)))
 in include/ansidecl.h after #define GCC_VERSION and I && this with the #if
FOO_CHECKING in rtl.h, tree.h, ira-int.h.


Alternatively, reject g++ < 3.4 entirely, or if enable-checking.
Or, well, I'm using -disable-bootstrap, and probably checking is never enabled
in the first phase anyway, so this all would just work if I didn't use that.
The patch is ok, but it might never make a difference if I didn't
-disable-bootstrap.


But I really really really like -disable-bootstrap, given how little I build,
which is still a very useful amount, it saves a ton (just libbackend.a and a
small frontend, no libraries, and I patched out gmp/mpfr/mpc dependencies, so
overall build is short even on slower machines (we run a range of machines..)).


  reply	other threads:[~2010-12-28 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  8:40 [Bug middle-end/46597] New: " jay.krell at cornell dot edu
2010-12-28 13:50 ` jay.krell at cornell dot edu [this message]
2021-12-23  7:27 ` [Bug middle-end/46597] " pinskia 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-46597-4-SPuG1e3o2f@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: link
Be 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).