From: "Holmes.Sherlock" <its.dipanjan.das@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Installing gcc 4.7.2 on Solaris 10 - SPARC platform
Date: Mon, 17 Dec 2012 00:09:00 -0000 [thread overview]
Message-ID: <1355702992125-898148.post@n5.nabble.com> (raw)
In-Reply-To: <fb8c575360f6.50cdfbe6@blastwave.org>
Dennis Clarke-2 wrote
> Success is measured via the testsuite so I would really like to know what
> sort of
> results you managed. Please.
Do you mean that even if it gets compiled and producing expected output for
a sufficiently large code, it MAY fail to produce correct code all the time?
Bean with my ignorance, I am new to this.
Dennis Clarke-2 wrote
> I have extensive experience with this ...
I know that you have, I already confirmed. :)
Dennis Clarke-2 wrote
> ...however I won't package nor aid in the distribution of a thing which is
> untested.
If running through testsuite is the acid test of certification, then I'd
also not want to package and release unless thoroughly tested. Still I have
the build directory lying on my system. I haven't run a gcc testsuite
earlier. Can you please let me know how to run a testsuite and post the
result back? Is it downloadable from somewhere? How to run it? Apart from
console log, does it produce any other log which I can post back?
--
View this message in context: http://gcc.1065356.n5.nabble.com/Installing-gcc-4-7-2-on-Solaris-10-SPARC-platform-tp894903p898148.html
Sent from the gcc - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-12-17 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:14 Dipanjan Das
2012-12-05 17:04 ` Dennis Clarke
2012-12-05 18:28 ` Holmes.Sherlock
2012-12-16 0:31 ` Holmes.Sherlock
2012-12-16 9:07 ` Kai Ruottu
2012-12-16 9:39 ` Holmes.Sherlock
2012-12-16 21:45 ` Dennis Clarke
2012-12-17 0:04 ` Holmes.Sherlock
2012-12-16 21:51 ` Dennis Clarke
2012-12-17 0:09 ` Holmes.Sherlock [this message]
2012-12-17 0:43 ` Dennis Clarke
2012-12-17 0:59 ` Holmes.Sherlock
2012-12-17 17:40 ` Tom Christensen
2012-12-17 17:49 ` Dennis Clarke
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=1355702992125-898148.post@n5.nabble.com \
--to=its.dipanjan.das@gmail.com \
--cc=gcc-help@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).