Hello,
On Tue, Sep 6, 2016 at 11:42 AM, Oleksij Rempel wrote:
> i'm one of ath9k-htc-firmware developers. Currently i'm looking for the
> way to provide this firmware as opensource/free package for debian. Main
> problem seems to be the need to patch gcc xtensa-config.h to make it
> suitable for
Hi Sterling,
I've got an issue building gdb for xtensa linux with gcc, reported it here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65416
Looking at it I've got two questions, can you help me with them?
1. in windowed ABI stack pointer update is always split into two opcodes:
add and movsp.
On Fri, Mar 13, 2015 at 8:08 PM, augustine.sterl...@gmail.com
wrote:
> On Fri, Mar 13, 2015 at 10:04 AM, Marc Gauthier wrote:
>> Other than the required 16-byte stack alignment, there's nothing in
>> the ABI that requires these extra 16 bytes. Perhaps there was a bad
>> implementation of the all
On Fri, Mar 13, 2015 at 11:18 PM, Segher Boessenkool
wrote:
> On Fri, Mar 13, 2015 at 05:54:48PM +0300, Max Filippov wrote:
>> 2. alloca seems to make an additional 16-bytes padding to each stack
>> allocation: alloca(1) results in moving sp down by 32 bytes, alloca(17)
>
On Fri, Apr 10, 2015 at 10:51 PM, augustine.sterl...@gmail.com
wrote:
> On Fri, Apr 10, 2015 at 12:15 PM, Max Filippov wrote:
>> Then configuration w/o multiplication should call helper at -O0 and
>> use shift at higher optimization levels?
>
> That is what I would expect
On Sat, Apr 11, 2015 at 2:16 AM, augustine.sterl...@gmail.com
wrote:
> On Fri, Apr 10, 2015 at 1:18 PM, Max Filippov wrote:
>> How can we have a mulsi3 pattern that don't get expanded until it's
>> optimized, and only gets expanded to a call if it couldn't be opt
Hello,
On Tue, Oct 16, 2018 at 1:54 PM Jim Wilson wrote:
>
> On 10/16/18 7:19 AM, Christophe Lyon wrote:
> > While reviewing one of my patches about FDPIC support for ARM, Richard
> > raised the concern of testing the patch on other uClinux targets [1].
> >
> > I looked at uclinux.org and at the
On Fri, Oct 26, 2018 at 6:51 AM Christophe Lyon
wrote:
> On Sun, 21 Oct 2018 at 04:06, Max Filippov wrote:
> > Probably the easiest way to get all xtensa toolchain parts correctly it
> > by using existing buildroot configuration. E.g. the following configuration
> > may be
On Wed, Oct 31, 2018 at 8:43 AM Christophe Lyon
wrote:
> I also built qemu from the branch you mentioned,
> and used the "run it on linux-user QEMU" section in the wiki
>
> I see many execution errors, now realizing that I didn't
> do what you said above: "apply gcc part of the xtensa overlay".
>
On Fri, Nov 2, 2018 at 3:29 AM Christophe Lyon
wrote:
> I re-ran the wiki instructions with --target=xtensa-buildroot-uclinux-uclibc
> and while gcc/g++ results looks mostly OK, the libstdc++ ones only show:
> Running ...f/trunk/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> ERROR: could not c
to fix it differently?
---8<---
>From bad901880a3f9fc69726aa082e2b2c674bacca94 Mon Sep 17 00:00:00 2001
From: Max Filippov
Date: Mon, 7 Jan 2019 18:22:12 -0800
Subject: [PATCH] gcc: move assemble_start_function / assemble_end_function to
output_mi_thunk
Let backends call assemble_start_fun
Hi Sterling,
for xtensa we have a number of bugfixes in the mainline that were never
backported to the stable branches. It'd be great having them in the stable
gcc releases instead of carrying the fixes in various toolchain builders.
Would it be ok to do the following backports?
to the gcc-5-bran
On Tue, May 30, 2017 at 3:34 PM, augustine.sterl...@gmail.com
wrote:
> On Tue, May 30, 2017 at 3:26 PM, Max Filippov wrote:
>> Hi Sterling,
>>
>> for xtensa we have a number of bugfixes in the mainline that were never
>> backported to the stable branches. It'd be
Hello,
I'm trying to build a canadian cross compiler with build == x86_64-linux,
host == xtensa-linux and target == xtensa-linux. I need to specify an
xtensa-specific flag in CFLAGS that will be applied to the host binary.
I put this flag into CFLAGS and CXXFLAGS. The first question: is that
the
On Mon, Nov 6, 2017 at 10:38 AM, Matias Fonzo wrote:
> On Mon, 6 Nov 2017 10:30:14 -0800
> Max Filippov wrote:
>
>> Hello,
>>
>> I'm trying to build a canadian cross compiler with build ==
>> x86_64-linux, host == xtensa-linux and target == xtensa-linux. I
Hi Waldemar,
On Tue, Nov 7, 2017 at 9:57 PM, Waldemar Brodkorb wrote:
>> I'm trying to build a canadian cross compiler with build == x86_64-linux,
>> host == xtensa-linux and target == xtensa-linux. I need to specify an
>> xtensa-specific flag in CFLAGS that will be applied to the host binary.
>
On Sun, Apr 1, 2018 at 4:34 AM, Jason Vas Dias wrote:
> In C++ however, it does not compile :
>
> $ g++ -g -std=gnu++11 -x c++ -c t.c
> t.c:5:8: error: 'void bar()' aliased to undefined symbol 'foo'
>void bar(void);
> ^
>
> Even though, if I compile the object with the declaration
>
On Sun, Apr 1, 2018 at 5:33 AM, Jason Vas Dias wrote:
> Aha! But how to determine the mangled name beforehand ?
>
> Even if I compile the object without the alias, then inspect
> the object with objdump, there is no mangled symbol
> _ZL3foov defined in the object file .
>
> So I must run some nam
Hi Alan,
On Thu, May 28, 2020 at 7:53 PM Alan Modra via Gcc wrote:
>
> On Thu, May 28, 2020 at 10:12:04AM -0700, augustine.sterling--- via Gcc wrote:
> > After a long run as the Xtensa port maintainer, it is time for me to move
> > on.
> >
> > I nominate Max Filippo
On Fri, Jun 5, 2020 at 5:50 PM David Edelsohn wrote:
> I am pleased to announce that the GCC Steering Committee has
> appointed Max Filippov as Xtensa maintainer.
Thank you for your trust.
> Please join me in congratulating Max on his new role.
> Max, please update
On Mon, Oct 31, 2022 at 1:23 PM Max Filippov wrote:
> I've been playing with a cross-compiler built with ASAN for
> target=xtensa-linux-uclibc and I was consistently getting a
> report for out-of-bound heap access inside IRA.
I'll file a bug report.
--
Thanks.
-- Max
Hi Suwa-san,
I've noticed that in xtensa configurations with hardware FPU
function arguments of type float are spilled on the stack although
there's no need for that. E.g. the following function:
int f(float a, float b)
{
return a < b;
}
translates to the following with -O2:
f:
entry
Hello.
This is a draft FDPIC ABI specification for the Xtensa architecture.
Please send comments. I will be implementing the final ABI version in
gcc and binutils.
The Xtensa FDPIC ABI
April 8, 2024
Version 1
Bas
23 matches
Mail list logo
