* Sergei Poselenov | 2010-09-22 15:49:39 [+0400]:
Hi Sebastian,
Hi Sergei,
I'm sorry I'm a bit slow in understanding - could you please answer my
further questions?
hehe, let's see.
Because the ABI is different. All you need to the same output as with
the tripplet you have to specify
Hi Sebastian,
On Tue, 21 Sep 2010 21:23:26 +0200
Sebastian Andrzej Siewior sebast...@breakpoint.cc wrote:
* Sergei Poselenov | 2010-09-21 14:54:22 [+0400]:
Hello Sebastian,
Hi Sergei,
Should the bug 44606 trigger on a e500v1 CPU?
I can check it with gcc 4.2.2 on a MPC8560 system.
SPE
Hi Sebastian,
I'm sorry I'm a bit slow in understanding - could you please answer my
further questions?
On Tue, 21 Sep 2010 21:18:47 +0200
Sebastian Andrzej Siewior sebast...@breakpoint.cc wrote:
* Sergei Poselenov | 2010-09-21 14:09:24 [+0400]:
Hello Sebastian,
Hi Sergei,
BTW, do you
Hello Sebastian,
On Sun, 19 Sep 2010 22:35:27 +0200
Sebastian Andrzej Siewior sebast...@breakpoint.cc wrote:
* Sergei Poselenov | 2010-09-18 11:44:01 [+0400]:
Thanks, but I'm looking for specific information - what instruction
set was used by gcc to build Debian binaries.
It seems to
Hello Sebastian,
Should the bug 44606 trigger on a e500v1 CPU?
I can check it with gcc 4.2.2 on a MPC8560 system.
Regards,
Sergei
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
* Sergei Poselenov | 2010-09-21 14:09:24 [+0400]:
Hello Sebastian,
Hi Sergei,
BTW, do you know - why the separate target for e500? Is the instruction
set for e500 so fundamentally different it needs a special configuration
for GCC? Why GCC cannot switch codegeneration at run-time, conditioning
* Sergei Poselenov | 2010-09-21 14:54:22 [+0400]:
Hello Sebastian,
Hi Sergei,
Should the bug 44606 trigger on a e500v1 CPU?
I can check it with gcc 4.2.2 on a MPC8560 system.
SPE support got merged in gcc 4.3. An e500v1 CPU does not have support
for the type double so you shouldn't be able run
* Sergei Poselenov | 2010-09-18 11:44:01 [+0400]:
Thanks, but I'm looking for specific information - what instruction set
was used by gcc to build Debian binaries.
It seems to me this information is not readily available... I can only
guess of gcc configuration - just defaults (-mcpu=powepc
Hello Sebastian,
Thanks for reply! Please see my comments below.
On Fri, 17 Sep 2010 20:19:29 +0200
Sebastian Andrzej Siewior sebast...@breakpoint.cc wrote:
* Sergei Poselenov | 2010-09-17 13:48:19 [+0400]:
Could you please answer some questions, regarding the use of the
Debian powerpc
Hello Xavier,
may be you can try apt-build ?
$ cat /etc/apt/apt-build.conf
build-dir = /var/cache/apt-build/build
repository-dir = /var/cache/apt-build/repository
Olevel = -O3
march = -march=pentium2
mcpu = -mcpu=pentium2
options =
As you can see, there you can rebuild packages in
Hi,
However, the auxiliary math routins in libgcc.a (.so) will be the same,
and
not optimized for the given CPU type.
Gcc compiler should be build with multilib support enabled, in this case
the build provides specialized libgcc.a and startup .o modules for each
possible -mcpu, in separate
Hello all,
Could you please answer some questions, regarding the use of the
Debian powerpc distro for embedded PowerPC system?
- What exact target CPU it is built for? I see here
http://www.debian.org/ports/powerpc/inst/install the list of
supported machines, but how can I understand will
On Fri, Sep 17, 2010 at 01:48:19PM +0400, Sergei Poselenov wrote:
- What exact target CPU it is built for? I see here
http://www.debian.org/ports/powerpc/inst/install the list of
supported machines, but how can I understand will the Debian binaries
work on my board with the specific CPU?
* Sergei Poselenov | 2010-09-17 13:48:19 [+0400]:
Could you please answer some questions, regarding the use of the
Debian powerpc distro for embedded PowerPC system?
- What exact target CPU it is built for? I see here
http://www.debian.org/ports/powerpc/inst/install the list of
supported
may be you can try apt-build ?
$ cat /etc/apt/apt-build.conf
build-dir = /var/cache/apt-build/build
repository-dir = /var/cache/apt-build/repository
Olevel = -O3
march = -march=pentium2
mcpu = -mcpu=pentium2
options =
As you can see, there you can rebuild packages in an automatic way with
15 matches
Mail list logo
