Sponsored Content
Full Discussion: Open source project
Top Forums Shell Programming and Scripting Open source project Post 302652181 by pludi on Wednesday 6th of June 2012 04:29:26 PM
Old 06-06-2012
A very simple start: pick the open source software you use most often, register with their bug tracking system, and start testing the newest builds. When something breaks, try to repeat it, and send it in with instructions on how to reproduce, what happens, ...

Over time you might start looking at the code to see why it breaks, or how to improve the documentation.
 

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Recruiting for an open source project

I am posting this gauge the level of interest among the community in forming an open source team to work on an automation harness I am about to make available. I already have a working POC running at my place of work, but it is not secure enough for production environments. However, I am about... (6 Replies)
Discussion started by: steadyonabix
6 Replies

2. Shell Programming and Scripting

Feedback on "withsome" open source project

I have been developing an open source UNIX project for a few years and am looking for feedback on whether further development of the "withsome" project is of interest to other programmers. One simple example to give an idea of the project is: withsome ./pugs vi Pugs.pm 1)... (0 Replies)
Discussion started by: ronaldxs
0 Replies
PAPI_ipc(3)							       PAPI							       PAPI_ipc(3)

NAME
PAPI_ipc - Simplified call to get instructions per cycle, real and processor time. SYNOPSIS
Detailed Description C Interface: #include <papi.h> int PAPI_ipc( float *rtime, float *ptime, long long *ins, float *ipc ); Parameters: *rtime total realtime since the first call *ptime total process time since the first call *ins total instructions since the first call *ipc incremental instructions per cycle since the last call Return values: PAPI_EINVAL The counters were already started by something other than PAPI_ipc(). PAPI_ENOEVNT The floating point operations event does not exist. PAPI_ENOMEM Insufficient memory to complete the operation. The first call to PAPI_ipc() will initialize the PAPI High Level interface, set up the counters to monitor PAPI_TOT_INS and PAPI_TOT_CYC events and start the counters. Subsequent calls will read the counters and return total real time, total process time, total instructions since the start of the measurement and the IPC rate since the latest call to PAPI_ipc(). A call to PAPI_stop_counters() will stop the counters from running and then calls such as PAPI_start_counters() or other rate calls can safely be used. PAPI_ipc should return a ratio greater than 1.0, indicating instruction level parallelism within the chip. The larger this ratio the more effeciently the program is running. See Also: PAPI_flips() PAPI_flops() PAPI_epc() PAPI_stop_counters() Author Generated automatically by Doxygen for PAPI from the source code. Version 5.2.0.0 Tue Jun 17 2014 PAPI_ipc(3)
All times are GMT -4. The time now is 06:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy