From: Ian Lance Taylor <iant@google.com>
To: David Fang <fang@csl.cornell.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: testresults limit?
Date: Wed, 06 Jul 2011 18:00:00 -0000 [thread overview]
Message-ID: <mcrzkkr70hp.fsf@coign.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1107061329330.3738@hal-00.csl.cornell.edu> (David Fang's message of "Wed, 6 Jul 2011 13:32:48 -0400 (EDT)")
David Fang <fang@csl.cornell.edu> writes:
> I'd like to post gcc testresults for 4.6.1 on powerpc-darwin8,
> but the length of my message (appx. 1MB due to large number of -flto
> failures) probably exceeds the mailing list's limit. What is this
> limit, and how would you recommend I prune the summary before
> re-sending it while keeping it meaningful?
The limit on mail to gcc-testresults is indeed 1M.
It doesn't seem useful to send a message which lists each individual lto
testsuite failure. As far as I can see the LTO tests are only run if
ENABLE_LTO is set. So take out the line "set ENABLE_LTO 1" from your
site.exp file.
Ian
prev parent reply other threads:[~2011-07-06 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 17:33 David Fang
2011-07-06 18:00 ` Ian Lance Taylor [this message]
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=mcrzkkr70hp.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=fang@csl.cornell.edu \
--cc=gcc@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).