Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix minor warnings in OSAL code #299

Merged
merged 2 commits into from
Dec 30, 2019

Conversation

jphickey
Copy link
Contributor

@jphickey jphickey commented Dec 9, 2019

Describe the contribution

Fix #298

Fix warnings that are triggered by compiling the OSAL coverage unit test with strict settings.

  • The OS_FPUExcAttachHandler() function needs to be prototyped as accepting a function pointer (not void*)
  • Const-Correctness on OS_ModuleLoad_Impl()
  • Use void* instead of char* for buffer pointer as the specific type is not known
  • Cast the function passed into taskSpawn() on VxWorks

Testing performed
Build code on all three supported OS's (POSIX, RTEMS, VxWorks) with full warnings and ENABLE_UNIT_TESTS=TRUE
Execute all unit tests and confirm passage
Execute cFE and confirm normal operation

Expected behavior changes
None.

System(s) tested on:

  • Ubuntu 18.04 LTS, 64-bit (native)
  • VxWorks 6.9 / MCP750 (GSFC build machine)
  • RTEMS 4.11 / i686 (running within QEMU)

Contributor Info
Joseph Hickey, Vantage Systems, Inc.

Community contributors
You must attach a signed CLA (required for acceptance) or reference one already submitted

Fix warnings that are triggered by compiling the OSAL coverage
unit test with strict settings.

- The OS_FPUExcAttachHandler function needs to be prototyped
  as accepting a function pointer (not void*)
- Const-Correctness on OS_ModuleLoad_Impl()
- Use void* instead of char* for buffer pointer as the specific
  type is not known
- Cast the function passed into taskSpawn on VxWorks
@jphickey jphickey force-pushed the fix-298-strict-warnings branch from 3110d25 to 2d27496 Compare December 9, 2019 20:35
Additional compiler warning fixes for the UT code itself.
This is committed separately from the changes that affect
the OSAL FSW code.
@skliper skliper added the CCB:Approved Indicates code review and approval by community CCB label Dec 18, 2019
@skliper skliper added this to the 5.1.0 milestone Dec 18, 2019
@skliper skliper changed the base branch from master to merge-20191230 December 30, 2019 21:06
@skliper skliper merged commit 31cc6ae into nasa:merge-20191230 Dec 30, 2019
skliper added a commit that referenced this pull request Dec 30, 2019
Fix #295, #298, #305, #307, #308,
    #313, #314, #316, #321, #323
Reviewed and approved at 2019-12-18 CCB
@jphickey jphickey deleted the fix-298-strict-warnings branch February 13, 2020 16:55
zanzaben added a commit to zanzaben/osal that referenced this pull request Jan 4, 2021
zanzaben added a commit to zanzaben/osal that referenced this pull request Jan 6, 2021
zanzaben added a commit to zanzaben/osal that referenced this pull request Jan 13, 2021
zanzaben added a commit to zanzaben/osal that referenced this pull request Jan 13, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
CCB:Approved Indicates code review and approval by community CCB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants