[rtems-source-builder commit] rtems4.11: OpenMP support for ARM, PowerPC, SPARC
chrisj at rtems.org
Sat Jul 18 23:57:29 UTC 2015
On 18/07/2015 11:38 pm, Sebastian Huber wrote:
> ----- Chris Johns <chrisj at rtems.org> schrieb:
>> On 18/07/2015 1:20 am, Joel Sherril wrote:
>>> diff --git a/rtems/config/4.11/rtems-arm.bset b/rtems/config/4.11/rtems-arm.bset
>>> index 1e06796..c0bd04a 100644
>>> --- a/rtems/config/4.11/rtems-arm.bset
>>> +++ b/rtems/config/4.11/rtems-arm.bset
>>> @@ -17,6 +17,11 @@
>>> %define enable_obsolete 1
>>> +# Enable OpenMP support
>>> +%define with_libgomp
>> I think this forces the option to be always on. Should a user be able to
>> disable the option with --without-libgomp ?
> More options more problems.
The more defaults we turn on the more regression testing we need to do.
The wiki page for OpenMP shows the test results status is unclear.
If we default to off and a user enables the feature that is different.
The need for regression testing and test results is not as critical.
> I don't think there are serious reasons to disable this option. If you don't need OpenMP, then you waste a couple of minutes in tool build time and some megabytes of disk storage.
I am not concerned about the time to build or disk space. I am concerned
about a change so close to the release plus I have not seen any test
results. I know it is difficult to make available features while they
are being worked on however it is also reasonable for users to expect it
basically works when on by default so it is the default status that
concerns me and what it says.
Are there test results that can be published for all the arch's enabled ?
How do we run the tests so we can regression test ?
FWIW gcc testing and the gcc testsuite is a big item we need to address
in a formal way so the whole regression testing of tools from building
to test results is available to all users and not hidden away on
developer machines with custom scripts.
More information about the devel