Bug 399007 - gnu.targets.M3/M4/M4F do not support 'clock()' and possibly other POSIX APIs
Summary: gnu.targets.M3/M4/M4F do not support 'clock()' and possibly other POSIX APIs
Status: CLOSED FIXED
Alias: None
Product: RTSC (ARCHIVED)
Classification: Technology
Component: Targets (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ashish Kapania CLA
QA Contact:
URL:
Whiteboard: target:3.24.07, 3.25.00
Keywords: readme
Depends on:
Blocks:
 
Reported: 2013-01-24 13:51 EST by Karl Wechsler CLA
Modified: 2013-04-04 17:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Wechsler CLA 2013-01-24 13:51:51 EST 
The xdctargets tests are failing for 6.34.06 release candidate because the test case is using TimestampStd.  TimestampStd uses clock() API.  And there's some problem linking code that uses clock().  See below.   SYS/BIOS programs have their own Timestamp modules that use native on-chip timers.  Typical SYS/BIOS apps do not trigger this problem.

 

All of the M3 and M4 GNU targets fail to link:

lnkm3g client_debug.xm3g ...

$LINUXPATH/libc.a(lib_a-timesr.o): In function `_times_r':

timesr.c:(.text+0x2): undefined reference to `_times'

collect2: ld returned 1 exit status

gmake: *** [] Error 1
Comment 1 Karl Wechsler CLA 2013-01-24 14:01:09 EST 
After talking with Alan, we think that the problem here might be a missing "stub" function for _times() that we need to provide.   This is just a guess, but thought I'd include this note in case the guess makes sense.
Comment 2 Dave Russo CLA 2013-03-13 19:44:39 EDT 
fixed in xdctools 3.25.00.46_eng
Comment 3 Dave Russo CLA 2013-03-13 19:46:03 EDT 
verified by successful pass of xdctest-c05, so the fix is included in xdctools 3.25.00.48