一个C测试套件（是：关于ARM的Rowley CrossWorks的意见） [英] A C test suite (was: Opinions on Rowley CrossWorks for ARM)
问题描述
David Brown写道：
Chris Hills写道：
> Paul Curtis< pl *@rowley.co.ukwrites
.... snip ...
>>>
您不能与BSI或ISO测试证书争论，不。您能否指导我为您所倡导的编译器提供此类证书？其中之一？
您可以从Plum Hall和Perennial测试套件开始吗？
我尝试了一个快速谷歌Plum Hall IAR，并查看了
第一个链接：
http://www.plumhall.com/cqs/tr/ trackrecord.html
似乎IAR是Plum Hall的客户，Red Hat也是如此。
这绝不意味着gcc是由Plum Hall认证的，但它确实看起来好像是认真对待测试套件测试。
来自Google的另一个有趣的发现：
http://gcc.gnu.org /ml/gcc/1998-07/msg00656.html
>离线我应该对编译器的认真讨论感兴趣
测试。
gcc测试套件的问题在于它适用于gcc
''标准''，而不是比ISO标准。一个测试套件应该是开源的，并且应该有几个（有一些共性的
），C90，C99和C0X各一个。测试
应与标准明确挂钩。有几个类需要测试
，即一致性，错误检测和
质量。最后一个将是有争议的。
Pascal测试套件的不幸体验是
警告。这很好，但移交给了一些英国公司
（我忘记了名字）并且基本上输了。它包括便携式手段
选择个别测试，以及进行全面检查。
因此GPL许可是必不可少的。
即使系统出现故障，结果也非常有用。对于
示例，如果编译器针对PIC，那么很多东西都是不可行的。运行套件会向用户指出这些构造
，然后用户可以避免使用它们。也许一个sourceforge
项目是否合适？这样的套件在开始时显然会很差，但应该会成熟。第一项任务是组织测试的方法
。 Pascal套件是一个很好的
例子。在
测试中应该没有压力包含C ++，这是一个完全独立的问题（和语言）。
从comp.arch.embedded转发到comp.lang.c和comp.std.c
-
Chuck F（cinefalconer at maineline dot net）
可用于咨询/临时嵌入式和系统。
< http://cbfalconer.home.att.net>
CBFalconer写道：
例如，编译器瞄准PIC的地方很多东西都是
不可行。
我很好奇，例如什么？
w ..
Walter Banks写道：
CBFalconer写道：
例如，在编译器针对PIC的情况下，很多事情都是不可行的。
我很好奇，例如什么？
w ..
有些PIC只有三层叠加。
Leon
2006年11月4日00:30:24 -0800，Leon < le ********* @ bulldoghome.com>
写道：
>
Walter Banks写道：
> CBFalconer写道：
例如，编译器针对的是PIC很多东西都简直不可行。
我很好奇，例如什么？
w ..
有些PIC只有三个等级堆。
我能想到的唯一问题是将（代码空间）返回
地址保存到数据地址空间RAM中。
通常情况下，即使这些PIC没有这样的功能，哈佛架构也有一些在代码和数据空间之间传输数据的方法，
实施C会有问题。只要间接跳转可以执行
，情况就不会无望。
Paul
David Brown wrote:
Chris Hills wrote:>Paul Curtis <pl*@rowley.co.ukwrites
.... snip ...
>>>
You can''t argue with an BSI or ISO test certificate, no. Can
you point me to such a certificate for the compilers you
advocate? One of them?
You can start with the Plum Hall and Perennial test suites?
I tried a quick google for "Plum Hall IAR", and looked at the
first link:
http://www.plumhall.com/cqs/tr/trackrecord.html
It would appear that IAR is a customer of Plum Hall, as is Red Hat.
That by no means implies that gcc is certified by Plum Hall, but it
does look like they take test suite testing seriously.
Another interesting find from google:
http://gcc.gnu.org/ml/gcc/1998-07/msg00656.html
>Off line I should be interested in a serious discussion on compiler
testing.
The problem with the gcc test suite is that it is geared to the gcc
''standard'', rather than the ISO standard. A test suite should be
open-source, and there should probably be several of them (with
some commonality), one each for C90, C99, and C0X. The tests
should be clearly tied to the standard. There are several classes
of tests needed, i.e. conformance, detection of errors, and
quality. The last will be controversial.
The unfortunate experience with the Pascal test-suite is a
warning. This was excellent, but handed over to some British firm
(I forget the name) and basically lost. It included portable means
of selecting individual tests, and of running an overall check.
Thus GPL licencing is essential.
The results should be very useful, even when systems fail. For
example, where a compiler is aimed at a PIC many things are simply
not feasible. Running the suite would point out those constructs
to the user, who can then avoid using them. Maybe a sourceforge
project would be appropriate? Such a suite would obviously be poor
at the start, but should mature. The first task would be a method
of organizing the tests. The Pascal suite is an excellent
example. There should be no pressure to include C++ in the
testing, that is an entirely separate issue (and language).
Xposted from comp.arch.embedded to comp.lang.c and comp.std.c
--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>
CBFalconer wrote:
For example, where a compiler is aimed at a PIC many things are simply
not feasible.I am curious, what for example?
w..
Walter Banks wrote:CBFalconer wrote:
For example, where a compiler is aimed at a PIC many things are simply
not feasible.
I am curious, what for example?
w..Some PICs only have three levels of stack.
Leon
On 4 Nov 2006 00:30:24 -0800, "Leon" <le*********@bulldoghome.com>
wrote:
>
Walter Banks wrote:>CBFalconer wrote:
For example, where a compiler is aimed at a PIC many things are simply
not feasible.
I am curious, what for example?
w..
Some PICs only have three levels of stack.The only problem I can think of is saving the (code space) return
address into the data address space RAM.
Usually even Harvard architecture have some means of transferring data
between code and data space, if these PICs do not have such feature,
implementing C would be problematic. As long as an indirect jump can
be performed, the situation is not hopeless.
Paul
这篇关于一个C测试套件（是：关于ARM的Rowley CrossWorks的意见）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
