From: Lawrence Crowl <crowl@googlers.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Richard Guenther <rguenther@suse.de>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
Diego Novillo <dnovillo@google.com>
Subject: Re: Convert more non-GTY htab_t to hash_table.
Date: Wed, 03 Oct 2012 16:55:00 -0000 [thread overview]
Message-ID: <CAGqM8fYGCseoRBK9K4JNzt3Ee=Wk8GH+wxXZN_MyLOW3GhPasQ@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8wxNeFnfibKAzqxGo3v5_2wTiCbP7GwH2pJ7pjQ9=kcPQ@mail.gmail.com>
On 10/2/12, Ian Lance Taylor <iant@google.com> wrote:
> On Oct 2, 2012 Lawrence Crowl <crowl@googlers.com> wrote:
> > On 10/2/12, Richard Guenther <rguenther@suse.de> wrote:
> > > You are changing a hashtable used by fold checking, did you
> > > test with fold checking enabled?
> >
> > I didn't know I had to do anything beyond the normal make check.
> > What do I do?
>
> Fold checking is not enabled by default because of high overhead
> and general pointlessness. To enable it, when you run configure,
> use --enable-checking=yes,fold.
So, why have the feature if it is pointless? Just curious.
--
Lawrence Crowl
next prev parent reply other threads:[~2012-10-03 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 21:54 Lawrence Crowl
2012-10-02 9:23 ` Richard Guenther
2012-10-02 19:10 ` Lawrence Crowl
2012-10-03 4:09 ` Ian Lance Taylor
2012-10-03 16:55 ` Lawrence Crowl [this message]
2012-10-03 16:57 ` Jakub Jelinek
2012-10-04 7:39 ` Richard Guenther
2012-10-04 18:03 ` Lawrence Crowl
2012-10-05 8:05 ` Richard Guenther
2012-10-05 20:59 ` Lawrence Crowl
2012-10-05 21:16 ` Jakub Jelinek
2012-10-05 22:08 ` Lawrence Crowl
2012-10-05 22:19 ` Diego Novillo
2012-10-08 19:26 ` Mike Stump
2012-10-03 22:43 ` Lawrence Crowl
2012-10-03 22:46 ` Lawrence Crowl
2012-10-05 21:03 ` Lawrence Crowl
2012-10-05 22:52 ` Diego Novillo
2012-10-09 21:22 ` Lawrence Crowl
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='CAGqM8fYGCseoRBK9K4JNzt3Ee=Wk8GH+wxXZN_MyLOW3GhPasQ@mail.gmail.com' \
--to=crowl@googlers.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=rguenther@suse.de \
/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).