search for: octos

Dear LLVMer ; i'm trying to use LLVM for a specific target, using different memory banks. I have written the frontend to generate a valid IR and want to use the existing passes (as defined in tool opt) to optimize the code. The target has specific instructions, so following advices given in documentation, I created an intrinsic function, with attribute [IntrReadArgMem]. My test case is

Hi, I'm currently deciding on what card to pruchase for octo/quad BRI card to use with Asterisk on EuroISDN lines. I'm aware of at least two options (Junghanns or Beronet), but don't know how stable and well supported they are. Which ones are better supported ? Any experiences? Any advice ? How tos ? What would you buy ? Thanks in advance, Regards, Rob.

On Thu, Dec 4, 2008 at 7:38 AM, Julien Schmitt <jschmitt at dibcom.fr> wrote: > Dear LLVMer ; > > i'm trying to use LLVM for a specific target, using different memory banks. > I have written the frontend to generate a valid IR and want to use the > existing passes (as defined in tool opt) to optimize the code. > > The target has specific instructions, so following

Hi, I'll soon replace a Junghanns OctoBRI with a Junghanns QuadBRI. As both use wcb4xxp driver (dahdi 2.3.0, libpri 1.4.10.2 and asterisk 1.6.1), I'm planning to proceed this way : 1. Edit 2 versions of files /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf (one for each card). 2. Link current system.conf and dahdi-channels.conf to QuadBRI files. 3. Power PC off 4. Swap cards

Hi, when building with the WITH_DEV conditional, either `libupsclient.pc' *or* `libupsclient-config' is installed. This is annoying when linking with libupsclient, because you basically have to do the check twice, once using `pkg-config' and once using `libupsclient-config'. Please consider the attached patch, which changes the behavior of `lib/Makefile.am' to install

>Submitter-Id: current-users >Originator: Dr. Otacon >Organization: Skimask Ninjas >Confidential: no >Synopsis: regchrome causes segfault during Mozilla build >Severity: critical >Priority: high >Category: ports >Class: sw-bug >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD octo.sytes.net 4.8-STABLE FreeBSD 4.8-STABLE #4: Wed Apr 9 14:48:08 MDT

tags 439986 upstream thanks Hi Florian, 2007/8/29, Florian Forster <octo at verplant.org>: > Package: nut-dev > Version: 2.2.0-1 > Severity: minor > > After upgrading from version 2.0.something to version 2.2.0-1 the type > `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for > software that is supposed to work with different versions of this >

On Tue, Nov 13, 2018 at 10:04:33AM +0000, Daniel P. Berrangé wrote: > On Fri, Nov 09, 2018 at 12:19:30PM +0000, Richard W.M. Jones wrote: > > Peter Dimitrov and myself were debugging a very peculiar bug when > > libguestfs is run as a plugin from collectd: > > > > https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 > > > > The long

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/

Hi, thank you very much for reporting this! Sounds like a bug in the exec plugin – it never ceases to amaze me how many issues a single plugin can have ;) > > > This means that any plugin that does the usual pattern of: > > > > > > pid = fork (); Note that the exec plugin is the *only* plugin that does this. All other plugins are forbidden to fork(), popen() or

Hi, Attached is small patch (based of r122998 of compiler-rt), required for clean builds on Solaris 10 / x86 using clang 2.8. Please consider it for inclusion. Cheers, Joakim -------------- next part -------------- A non-text attachment was scrubbed... Name: solaris_stdint.patch Type: application/octet-stream Size: 457 bytes Desc: not available URL:

Thanks Eli. I will try your solution, but then, what is the difference between [IntrReadArgMem] and [IntrReadMem] when specifying an intrinsic ? It seems that both options specify that a function is 'readonly' (maybe the difference is not well supported for then moment ?) Julien > Dead store elimination is that pass that could do the optimizations in > question. The second

A quick glance shows that the exec plugin actually is clearing the signal mask: https://github.com/collectd/collectd/blob/master/src/exec.c#L526 Can you give some more context when this problem comes up? Ideally in a Github issue (hint, hint ;). -- Florian octo Forster Hacker in training GnuPG: 0x0C705A15 http://octo.it/

Good day all I've installed a few systems with quad/octo bri cards On these systems incoming numbers are ether the full number,example 12345657 or ether the last 4 digits,example 7654 But for some reason the latest installation incoming numbers comes in as extension "s"?? Is this something to do with the telecoms provider or a asterisk config? Please Help ore advice Thanks Altus

Hi, I guess I'd need to run Beronet quad and octo bri cards under bristuff to get zaptel features (echo canceling, timing source).... Am I right or could I achieve this also with chan_misdn - their native driver ? Running bristuff on Beronet cards is unsupported. Has anyone succesfully run Beronet quad BRI cards under bristuff recently ? Do they work ? Regards, Rob.

For reasons unknown, any connections to localhost -- tcp, icmp, or udp -- are all originating from my external interface, rl0: $ telnet localhost 25 Trying ::1... Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Can't assign requested address telnet: Unable to connect to remote host IPFW log: Jul 16 12:46:43 octo ipfw: 100 Accept TCP 192.168.1.119:1434 127.0.0.1:25 out via rl0

> Hi all, Hi Marco, > I was thinking about integrating an old PBX with Asterisk and I was wondering > some possible configurations. You didn't mention the number of lines your PBX uses, but think of a third scenario: Install an asterisk with twice the number of BRI/PRI-Ports your current PBX has. Connect half of them to your carrier, the other ones to your old PBX (Some sort of

> > Its up to 5.8G of resident memory with 28321 calls processed. > The OOM killer is going to kill this soon at this rate (8GB RAM machine). > This seems like a pretty serious problem. > It looks like I'll need to restart asterisk every night.... Hi the number of cpu cores that you see with top times 512Mbyte is the level of ram that's needed e.g. a hp-gen8 with 2 octo

Hi, I've stumbled upon a problem which I can't solve easily with the available options in tinc - at least as far as I see. If enlightenment is all I need, I'll happily accept pointers ;) I try to establish a connection between two hosts. Each host has multiple addresses assigned to it's internet interface. A stripped down list would be: Host 1: 2001:780:0:1e::1

Hi, Has anyone information about BRI hardware supported by 1.6 libpri ? In another thread, I was told a basic BRI card with HFC chipset (Bewan Gazel 128) was supported but I would delighted to lear about other harwarde (and specifically about Digium B410P). Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: