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

Tags

Special Forums News, Links, Events and Announcements Software Releases - RSS News Vector Signal Imaging Processing Library 1.4 (Sourcery VSIPL++ branch)

06-30-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

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...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

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?

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!

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" ...

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...

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....

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...

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...

LEARN ABOUT REDHAT

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)

Software Releases - RSS News