similar to: ARM4 filter code

The attached patch eliminates some warnings while compiling for ARM4 targets. It also simplifies the asm constraints a bit. Now we can use the ARM4 optimisations when compiling for PortalPlayer targets in Rockbox. Cheers, Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: speex_arm4.patch Type: text/x-diff Size: 1550 bytes Desc: not available Url :

On Wed, Mar 14, 2018 at 8:55 AM Christopher Lameter <cl at linux.com> wrote: > On Wed, 14 Mar 2018, Peter Zijlstra wrote: > > On Tue, Mar 13, 2018 at 01:59:24PM -0700, Thomas Garnier wrote: > > > @@ -1576,7 +1578,9 @@ first_nmi: > > > addq $8, (%rsp) /* Fix up RSP */ > > > pushfq /* RFLAGS */ > > > pushq

Hello. I am playing with LLVM and trying to make Z80 (Zilog Z80) backend. The source code is attached. I have succesfully made some simple test. But now I have problem with ADD instruction. The source C code is: typedef struct { unsigned char id1; unsigned char id2; unsigned char id3; } testS; void simple() { testS test; test.id1 = 0x40; test.id2 = 0x80; test.id3 = 0xc0; } It

Hi Peter, I think the problem is that you did not explicitly define stack alignment in Z80TargetMachine.cpp DataLayout("e-p:16:8:8-i8:8:8-i16:8:8-i32:8:8-n8") Try to add S16 to the string if your stack is 2-byte aligned. Refer to http://llvm.org/docs/LangRef.html#datalayout . If it does not work, try to specify the layout in the input module using target layout directive. David On

All, Attached is a patch that does two things. First it makes the use of the current SSE code a run time option through the use of speex_decoder_ctl() and speex_encoder_ctl It does this twofold. First there is a modification to the configure.in script which introduces a check based upon platform. It will compile in the sse assembly if you are on an i?86 based platform by making a

Hello. I have played with DataLayout and found a solution with is uknown to me. I added S16 and also s0:16:16, but it had not worked. Then I found that in Z80FrameLowering.h I am calling TargetFrameLowering with stack aligment set to 8. So I changed it to 2 bytes. But this also didn't help. Then I changed llc to show TargetDataLayout and found that a option is set to a0:0:64. So I changed

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

Hi?Jean-Marc? Thanks for your suggestions very much! > > I am porting speex on ARM7TDMI, I have done some optimization, the > > result is that the encoder and decoder need about 60 MCPS for 5.96kbps > > bitrate and complexity 0. Can someone give me informtion about Speex > > optimization on ARM7? > > That's quite good. A few suggestions here: > 1) Don't

Alexander Chemeris a ?crit : > Ok, if I comment out inclusion of "filters_arm4.h" (or comment out its > only overridden function - normalize16()) it works fine. > > Also it works fine if I use -O0 for compilation. Specifying -O1 or -O2 lead > to segfault (if "filters_arm4.h" is included, sure). OK, so either I screwed up the alignment/constraints in the

> Yes, I have enabled the the current ARM4 assembly bits. I have tried > to optimize these functions(filter_mem16(),iir_mem16() and > fir_mem16()) in C code, but the effect is very small, and I am going > to do assembly optimization for these functions. Do you have another C > code about these functions for assembly optimisations? Can you give me > some information and

Who's "shouting" here? Even in complete lines, 9 consecutive words! PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.c clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.sh clang: note: diagnostic msg: ******************** --- crash-74a40f.c ---

"David Blaikie" <dblaikie at gmail.com> wrote: > Context is everything. I'm willing to accept your humble apologies. > Spotting the relevant details in long build output > can be tricky & some emphasis (caps, the *** borders, etc) can be useful. So you dare to "shout" at your users/customers, but mock when someone (me) uses the same sort of emphasis,

Content-Type: multipart/related; boundary="------------DB3A3FF1.D25D383D" --------------DB3A3FF1.D25D383D Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <body bgcolor=3D"#ffffff" text=3D"#000000"> <img src=3D"cid:891A9257=2E4479B8C9"> <br> We awaken in others the same

Hi Stefan, You can find the contribution guidelines here : https://llvm.org/docs/Contributing.html LLVM also have code of conduct : https://llvm.org/docs/CodeOfConduct.html On Sun, 23 Aug 2020 at 23:28, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Sun, Aug 23, 2020 at 10:54 AM Stefan Kanthak <stefan.kanthak at nexgo.de> > wrote: > >>

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

-----Original Message----- From: Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> To: ??????? ??????? <altersoft at mail.ru> Date: Sat, 02 Aug 2008 07:54:34 -0400 Subject: Re: [Speex-dev] fir_mem16,iir_mem16 and filter_mem16 optimisations > > ??????? ??????? a ?crit : > > I have some questions about that functions: fir_mem16, iir_mem16 and filter_mem16. > >