> But I'm not building for thumb, on the contrary, that code I'm
> compiling is performance sensitive and I don't want to use thumb at
> all.
> MS compilers are way behind gcc in this regard, the latest what they
> support is armv5e. But it doesn't mean that you can't use instructions
> supported b
> -Original Message-
> From: Pedro Alves [mailto:pe...@codesourcery.com]
> Sent: March 15, 2010 15:46
> To: cegcc-devel@lists.sourceforge.net; danny.ba...@scarlet.be
> Cc: Pavel Pavlov
> Subject: Re: [Cegcc-devel] Ws2tcpip.h
>
> On Monday 15 March 2010 19:33:41, Danny Backx wrote:
> > >
> On Mon, 2010-03-15 at 13:09 -0400, Pavel Pavlov wrote:
> > If you are using 4.4.0, can you test this code:
> >
> > #include
> > int main(int argc, char **argv){
> > return (long) &VirtualAlloc;
> > }
> >
> > 1) with -march=armv5te (works ok)
> > 2) with -march=armv7 (error: target CPU d
On Mon, 15 Mar 2010, Pedro Alves wrote:
> On Monday 15 March 2010 19:44:01, Danny Backx wrote:
>>> So, is there some fixes that has been pushed in svn about that limits.h
>>> problem ?
>>>
>>> Vincent Torri
>>
>> My workaround was removed, I've not taken action on this issue since.
>
> I haven't
On Monday 15 March 2010 19:44:01, Danny Backx wrote:
> > So, is there some fixes that has been pushed in svn about that limits.h
> > problem ?
> >
> > Vincent Torri
>
> My workaround was removed, I've not taken action on this issue since.
I haven't had time to finish fixing the issue properly.
On Monday 15 March 2010 19:33:41, Danny Backx wrote:
> > 3) with -mcpu=cortex-a8 (Assembler messages: Error: cannot represent
> > BFD_RELOC_ARM_MOVW relocation in this object file format)
> >
> > Does it mean that there is no proper support for newer cpu's in the version
> > of binutils that com
On Sun, 2010-03-14 at 08:55 +0100, Vincent Torri wrote:
> So, is there some fixes that has been pushed in svn about that limits.h
> problem ?
>
> Vincent Torri
My workaround was removed, I've not taken action on this issue since.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; h
On Mon, 2010-03-15 at 13:25 +0100, Vincent Richomme wrote:
> Ok when reading some post on mingw mailing list,I could read the following
> lines :
>
> "With those conditions, the lack of an -enable-auto-import switch does
> not
> cause the 0xc005 error that ld warns about here:
>
> It look
On Mon, 2010-03-15 at 13:09 -0400, Pavel Pavlov wrote:
> > On Sun, 2010-03-14 at 20:15 -0400, Pavel Pavlov wrote:
> > > > On Sun, 2010-03-14 at 04:25 -0400, Pavel Pavlov wrote:
> > > > > Sorry, I should have give more info. Off course default vanilla
> > armv4
> > > > will work,
> > > > > but I nee
> On Sun, 2010-03-14 at 20:15 -0400, Pavel Pavlov wrote:
> > > On Sun, 2010-03-14 at 04:25 -0400, Pavel Pavlov wrote:
> > > > Sorry, I should have give more info. Off course default vanilla
> armv4
> > > will work,
> > > > but I need to enable armv7 + neon compilation. Currently, It
> won't
> > > c
On Sun, 2010-03-14 at 20:15 -0400, Pavel Pavlov wrote:
> > On Sun, 2010-03-14 at 04:25 -0400, Pavel Pavlov wrote:
> > > Sorry, I should have give more info. Off course default vanilla armv4
> > will work,
> > > but I need to enable armv7 + neon compilation. Currently, It won't
> > compile the
> > >
On Sat, 13 Mar 2010 09:47:09 +0100, Danny Backx
wrote:
> On Wed, 2010-03-10 at 21:15 +0100, Danny Backx wrote:
>> Meaning, I think, that it does indeed crash in that statement. The
>> double "ldr r3, [r3]" seems odd. Even more odd is that the code in
>> a/t.dll.objdump is different : it looks exac
On Sun, 14 Mar 2010 20:15:51 -0400, Pavel Pavlov
wrote:
>> On Sun, 2010-03-14 at 04:25 -0400, Pavel Pavlov wrote:
>> > Sorry, I should have give more info. Off course default vanilla armv4
>> will work,
>> > but I need to enable armv7 + neon compilation. Currently, It won't
>> compile the
>> > cod
13 matches
Mail list logo
