Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Loop vectorizer preamble"
2015 Jan 01
2
PJSIP / T.38 - Asterisk not passing on v21 preamble and data
Dear list,
happy new year!
I am still trying to make T.38 work. In the meantime, I have upgraded to Asterisk 13.1.0, and I am using the most recent PJSIP library (compiling that stuff myself). My local fax software is capable of T.38, as is my ITSP; Asterisk sits in the middle, of course. Asterisk is in the same private subnet as the local fax software and talks to the ITSP through a NAT'd
2013 Nov 16
0
[LLVMdev] Limit loop vectorizer to SSE
I confirm that r194876 fixes the issue, i.e. segfault not caused.
My program still passed 16 byte aligned pointers to the function
which the loop vectorizer processes successfully:
LV: Vector loop of width 8 costs: 1.
LV: Selecting VF = : 8.
LV: Found a vectorizable loop (8) in func_orig.ll
LV: Unroll Factor is 1
Since the program runs fine, it seems to be allowed for the CPU
to issue a vector
2013 Nov 16
1
[LLVMdev] Limit loop vectorizer to SSE
The vectorizer will now emit
= load <8 x i32>, align #TargetAlignmentOfScalari32
where before it would emit
= load <8 x i32>
(which has the semantics of “= load <8 xi32>, align 0” which means the address is aligned with target abi alignment, see http://llvm.org/docs/LangRef.html#load-instruction).
When the backend generates code for the former it will emit an unaligned move:
2004 Jan 08
4
Add a preamble to documentation
Hi list, hi John,
having seen last week a post (see
http://marc.theaimsgroup.com/?m=107341768923846) that remind me some
quirks I encountered, I'd like to see a preamble added to the chapter 12
of the howto. It concerns the diffent types of admin you will need in a
PDC setup.
I say preamble, but it could be found anywhere else, as long as it could
be found (I have lost long hours
2013 Nov 15
2
[LLVMdev] Limit loop vectorizer to SSE
A fix for this is in r194876.
Thanks for reporting this!
On Nov 15, 2013, at 3:49 PM, Joshua Klontz <josh.klontz at gmail.com> wrote:
> Nadav,
>
> I believe aligned accesses to unaligned pointers is precisely the issue. Consider the function `add_u8S` before[1] and after[2] the loop vectorizer pass. There is no alignment assumption associated with %kernel_data prior to
2015 Jan 06
0
PJSIP / T.38 - Asterisk not passing on v21 preamble and data
Hi,
On Thu, Jan 1, 2015 at 7:09 PM, Recursive <lists at binarus.de> wrote:
> 1) Did anybody test T.38 with SPANDSP? If yes, which version of SPANDSP did you use? Mine is 0.0.6 PRE 20. Should I try to upgrade to PRE 21? Or to one of the snapshots?
I remember that I was having issues with an older libspandsp library.
I simply upgraded to the latest available version which made the issue
2008 Apr 21
2
[LLVMdev] getting started with IR needing GC
On Apr 20, 2008, at 6:52 PM, Gordon Henriksen wrote:
> On 2008-04-20, at 21:05, Terence Parr wrote:
>
>> On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote:
>>
>>> Since the semispace heap doesn't actually work (it's an example,
>>> at best), I suggest you simply copy the stack visitor into your
>>> project; it's only a dozen lines of
2009 May 20
2
Problems receiving some faxes in T.38
Hello,
We have been working with the ReceiveFax application for some weeks now in
order to receive faxes in T.38 and it works fairly well, but there are some
faxes that for some reason we are not able to receive correctly.
The asterisk version we are using is 1.6.0.6 with spandsp-0.0.5pre4 and the
asterisk machine is behind a CISCO mediaGW to be able to communicate with
the PSTN.
The SIP call
2013 Dec 12
3
[LLVMdev] LLVM 3.4 Branch Freeze
The LLVM 3.4 branches are now frozen. We’re only accepting major, super horrible bug fixes from now on. The testers are going to do a third phase of testing, but it’s mostly to verify that we don’t have any major problems left.
Share and enjoy!
-bw
2015 Jul 16
2
[LLVMdev] Improving loop vectorizer support for loops with a volatile iteration variable
----- Original Message -----
> From: "Chandler Carruth" <chandlerc at google.com>
> To: "Hyojin Sung" <hsung at us.ibm.com>, llvmdev at cs.uiuc.edu
> Sent: Wednesday, July 15, 2015 7:34:54 PM
> Subject: Re: [LLVMdev] Improving loop vectorizer support for loops
> with a volatile iteration variable
> On Wed, Jul 15, 2015 at 12:55 PM Hyojin Sung
2015 Jul 16
2
[LLVMdev] Improving loop vectorizer support for loops with a volatile iteration variable
----- Original Message -----
> From: "Chandler Carruth" <chandlerc at google.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Hyojin Sung" <hsung at us.ibm.com>, llvmdev at cs.uiuc.edu
> Sent: Thursday, July 16, 2015 1:06:03 AM
> Subject: Re: [LLVMdev] Improving loop vectorizer support for loops
> with a volatile iteration
2012 Apr 14
1
Sweave UFT8 problem
Hi,
I work on MacOS, trying to Sweave an UFT8 document.
AFAI remember R 2.14 used to render a warning when the encoding was not
declared when using Sweave.
With R 2.15 it seems to render an error.
Sweave("sim_pi.Rnw")
Error: 'sim_pi.Rnw' is not ASCII and does not declare an encoding
Declaring an encoding by adding a line like
\usepackage[utf8]{inputenc}
in the preamble does
2004 Jan 12
0
About - Add a preamble to documentation
Hi, I need to use other user than root for join the pc's to the Samba 3 PDC
I Try the groupmap option for this:
[root@bch:/]# /usr/local/samba/bin/net groupmap list
System Operators (S-1-5-32-549) -> -1
Replicators (S-1-5-32-552) -> -1
Guests (S-1-5-32-546) -> -1
Domain Users (S-1-5-21-107229157-1068619686-3350107674-513) -> -1
Domain Admins
2014 Oct 14
1
debugging T.38 issues
Hello list,
We're currently facing some issues concerning T.38 gateway faxing.
This is a device used almost exclusively for receiving faxes. Calls
are incoming to asterisk on a SIP trunk (sangoma netborder) using
G711A. Gateway mode is activated in the asterisk dialplan towards a
Cisco SPA 112 running firmware 1.3.5. We are using asterisk 1.8.13.0
with the T.38 gateway patch applied (I know I
2006 Mar 14
1
I''m missing something obvious to a taglib programmer ...
I am trying to create, display and edit a referenced object''s text field
on the same view as my root object. I have just about come to the
conclusion that whoever invented of taglibs should be shot.
quiz.preamble_presentation references a Presentation object instance.
The Presentation object contains a property called text, among others.
The generated form will display the ID of the
2006 Mar 09
2
Newbie question: How to represent parent-child denormalization
I am building a relatively trivial application to try to learn my way
around Rails. I am having difficulty understanding how to navigate a
heavily denormalized hierarchy. Could someone direct me to a bare-bones
explanation of using rails to navigate database hierarchies?
I am an experienced developer. Most of my work has been desktop client
server, high performance, or server to server
2008 May 19
2
[LLVMdev] LLVM on small MCUs?
On Mon, 2008-05-19 at 20:40 +0300, Pertti Kellomäki wrote:
> The only hitch is that in the MCU world people expect to be
> able to write interrupt handlers and the like in C...
Most of the support that I have seen for this in other compilers amounts
to custom calling conventions and preambles. Are you thinking of more
than this?
2001 Dec 01
1
Jobnames displayed by lpq: Fixed a bit
There has been some correspondence about getting the file names displayed
with lpq instead of the smbXXXXX name. The -J option works, but, with some
documents, notably Microsoft Word and Corel WP9, the application sends a
long preamble, such that the file name is never seen in the queue when
listed with lpq.
eg:
Microsoft Word - PRINT FILE NAME.doc
So, to fix this up, at least for word documents,
2011 Jan 21
5
What the??? Failing dependancies and not sure why...
Observe the following code sniget:
user {
nagios :
comment => "Nagios Host Monitoring Service",
shell => "/bin/bash",
home => "/home/nagios",
ensure => present
}
file {
nagios-homedir :
path => "/home/nagios",
owner => "nagios",
2013 Dec 13
0
[LLVMdev] [cfe-dev] LLVM 3.4 Branch Freeze
Bill, et al.,
There are still a number of open bug reports demonstrating miscompiles on x86 with small/reduced test cases. I propose that we either delay this release until these have been fixed, or plan on a point release in the near future. I recommend that we put out another two release candidates, one at the end of this week, and one after another two weeks or so, to allow for these