06-30-2008
Vector Signal Imaging Processing Library 1.4 (Sourcery VSIPL++ branch)
The Vector Signal Image Processing Library is an application programming interface (API) defined by an open standard. This package is a reference implementation of this specification.
License: GNU General Public License (GPL)
Changes:
This release implements return-block optimization (RBO). It improves and increases the usage of high-performance math libraries. It improves and increases the usage of SIMD instructions. The API has been extended to include optimized implementations of threshold, axpy, maxval, and minval. Performance of computations involving sparse matrices and tensors has been improved. There are assorted bugfixes.
More...
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Can any body give example of using Unix Signals. What I want to do is
I am running a sql query in a shell script
I want, if sql query exceed the defined no. of seconds limit, then I would like to kill the process.
I know this can be done thru Unix Signal Handling but I do not know... (8 Replies)
Discussion started by: sanjay92
8 Replies
2. Programming
i am trying to use the history functions in a c++ program along with a custom signal handler for SIGINT.
the prog works fine catching signals without the line:
add_history(*args);
but as soon as this line is added, the prog segfaults on SIGINT.
does anyone have experience using gnu... (2 Replies)
Discussion started by: a1g0rithm
2 Replies
3. Shell Programming and Scripting
I am trying to develop a script that will properly handle kill signals particularly kill -2. I have program (_progres) that properly receives the signal if I run it from the command line directly:
_progres -T /tmp -p /home/mejones/signal.p -b 2>&1 &
If I try to put it in a script (i.e.... (2 Replies)
Discussion started by: mejones99
2 Replies
4. Programming
We have written a deamon which have many threads.
We are registering for the SIGTERM and trying to close main thread in this signal handling. Actually these are running on Mac OS X ( BSD unix). When we are unloading the deamon with command launchctl, it's sending SIGTERM signal to our process... (1 Reply)
Discussion started by: Akshay4u
1 Replies
5. Programming
I'm writing a function right now, and I want to set an alarm to avoid a timeout, here's the general idea of my code:
int amt = -2;
alarm(10);
amt = read(fd, &t->buf, TASKBUFSIZ - tailpos); //do a read
when the alarm goes off, i want to check the value of "amt"
... (1 Reply)
Discussion started by: liaobert
1 Replies
6. Solaris
I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM.
Can someone tell me what is the behavioral difference among these 3 signals in kill command?
Thanks! (2 Replies)
Discussion started by: joe228
2 Replies
7. Shell Programming and Scripting
Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
LEARN ABOUT HPUX
archpath
ARCHPATH(1) General Commands Manual ARCHPATH(1)
NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches
SYNOPSIS
archpath
archpath branch
archpath branch--version
DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy.
In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working
copy.
If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current
archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current
archive and category and with the same version as the current working copy.
This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com-
mand like this:
baz branch $(archpath) $(archpath new-feature)
Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this:
baz branch $(archpath) $(archpath releases--1.0)
That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result.
AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public
License, version 2 or later.
DEBIAN
Debian Utilities ARCHPATH(1)