Vector Signal Imaging Processing Library 1.4 (Sourcery VSIPL++ branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Vector Signal Imaging Processing Library 1.4 (Sourcery VSIPL++ branch)
# 1  
Old 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.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Continue Processing after a signal is caught

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

2. Solaris

Signal Processing in unix

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

3. Programming

alarm signal processing

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

4. Programming

Signal processing

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. Shell Programming and Scripting

Script Signal Processing

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

6. Programming

gnu history library signal segfault

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

7. UNIX for Dummies Questions & Answers

Signal Processing

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
Login or Register to Ask a Question
Signal(3pm)						User Contributed Perl Documentation					       Signal(3pm)

NAME
IPC::Signal - Utility functions dealing with signals SYNOPSIS
$number = sig_num $name; $name = sig_name $number; sig_translate_setup; $number = $Sig_num{$name}; $name = $Sig_name[$number]; DESCRIPTION
This module contains utility functions for dealing with signals. Nothing is exported by default. sig_num chopped-signal-name Returns the signal number of the signal whose name (sans "SIG") is chopped-signal-name, or undef if there is no such signal. This function is prototyped to take a single scalar argument. sig_name signal-number Returns the chopped signal name (like "HUP") of signal number signal-number, or undef if there is no such signal. This function is prototyped to take a single scalar argument. sig_translate_setup If you want to use the @Sig_name and %Sig_num variables directly you must call sig_translate_setup to initialize them. This isn't nec- essary if you only use the function interfaces sig_name() and sig_num(). This function is prototyped to take no arguments. %Sig_num A hash with chopped signal name keys (like "HUP") and integer signal number values. @Sig_name An array mapping signal numbers to chopped signal names (like "HUP"). AUTHOR
Roderick Schertler <roderick@argon.org> SEE ALSO
perl(1). perl v5.8.8 1998-12-28 Signal(3pm)