Hi,
Lennart Sorensen wrote:
On Thu, Jul 07, 2016 at 01:43:12PM +0200, Gabriel Paubert wrote:
>You don't always configure/compile on the machine you run. Especially
>the people who build distributions.
True, but you would still be configuring and compiling against the target
libc, so configure
On Thu, Jul 07, 2016 at 01:43:12PM +0200, Gabriel Paubert wrote:
> You don't always configure/compile on the machine you run. Especially
> the people who build distributions.
True, but you would still be configuring and compiling against the target
libc, so configure would do the right thing.
--
On Thu, Jul 07, 2016 at 10:52:01AM +0200, Riccardo Mottola wrote:
> I wonder if you can have different cores? e.g. how is a Cell processor seen
> in cpuinfo? Just out of curiosity.
I don't think it is, since it needs special handling to dispatch jobs.
As long as any core in cpuinfo has altivec, it
Hi,
Gabriel Paubert wrote:
Anyway, I think the best of two worlds would be to use getauxval()
>when available (most probably any currently supported OS) and fall
>back to cpuinfo if not. A configure test I suppose is quite simple.
You don't always configure/compile on the machine you run. Espec
On Thu, Jul 07, 2016 at 10:52:01AM +0200, Riccardo Mottola wrote:
> Hi,
>
> Gabriel Paubert wrote:
> >>That is garbage in my opinion, given there exists a proper interface
> >>>for getting that info.
> >Seconded, getauxval (not getauxvec!) is simpler, officially supported
> >for a long time, and w
Hi,
Gabriel Paubert wrote:
That is garbage in my opinion, given there exists a proper interface
>for getting that info.
Seconded, getauxval (not getauxvec!) is simpler, officially supported
for a long time, and while the intent is not to modify the format of
/proc/cpuinfo in a way that would br
On Wed, Jul 06, 2016 at 04:54:01PM -0400, Lennart Sorensen wrote:
> On Wed, Jul 06, 2016 at 09:54:02PM +0200, Riccardo Mottola wrote:
> > "upstream" replied with this:
> >
> > https://github.com/libjpeg-turbo/libjpeg-turbo/commit/6c0b7613b4d48dd35e54fc968f4a808d495f2fef
>
> That is garbage in my
On Wed, Jul 06, 2016 at 09:54:02PM +0200, Riccardo Mottola wrote:
> "upstream" replied with this:
>
> https://github.com/libjpeg-turbo/libjpeg-turbo/commit/6c0b7613b4d48dd35e54fc968f4a808d495f2fef
That is garbage in my opinion, given there exists a proper interface
for getting that info.
> parsi
Hi,
Lennart Sorensen wrote:
Actually it appears it will, but it requires gcc that was built against
glibc 2.23 which just entered unstable. Before glibc 2.23, gcc on
powerpc does not supprot those builtins.
I will try to do a patch that does getauxvec of AT_HWCAP directly instead
to get altive
On Wed, Jul 06, 2016 at 11:25:34AM +0200, Riccardo Mottola wrote:
> Hi,
>
>
> Mathieu Malaterre wrote:
> >Well it does not work -yet- at least on ppc32 with gcc 6.1.1:
> >
> >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71777
> >
> >But I would report the bug anyway to libjpegturbo. Riccardo, cou
Hi,
Mathieu Malaterre wrote:
Well it does not work -yet- at least on ppc32 with gcc 6.1.1:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71777
But I would report the bug anyway to libjpegturbo. Riccardo, could you do that?
reported upstream:
https://github.com/libjpeg-turbo/libjpeg-turbo/is
On Tue, Jul 5, 2016 at 9:01 PM, Lennart Sorensen
wrote:
> On Tue, Jul 05, 2016 at 07:46:10PM +0200, Riccardo Mottola wrote:
>> Hi Lennart,
>>
>> Lennart Sorensen wrote:
>> >On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
>> >>I what test program could I use? I noticed that e.g. F
On Tue, Jul 05, 2016 at 07:46:10PM +0200, Riccardo Mottola wrote:
> Hi Lennart,
>
> Lennart Sorensen wrote:
> >On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
> >>I what test program could I use? I noticed that e.g. Firefox (which works)
> >>is not linked against it.
> >You could
Hi Lennart,
Lennart Sorensen wrote:
On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
I what test program could I use? I noticed that e.g. Firefox (which works)
is not linked against it.
You could try forcing altivec off in libjpegturbo by setting the environment:
export JSIMD
too.
Luigi
Da: mathieu.malate...@gmail.com per conto di
Mathieu Malaterre
Inviato: martedì 5 luglio 2016 08.18
A: Lennart Sorensen
Cc: Riccardo Mottola; PowerPC List Debian
Oggetto: Re: jpeg-turbo 6.2 and ppc G3
On Mon, Jul 4, 2016 at 6:45 PM, Lennart Sorensen
On Mon, Jul 4, 2016 at 6:45 PM, Lennart Sorensen
wrote:
> On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
>> Hi,
>>
>> any of you still running G3 or anyway a non-altivec computer?
>>
>> I noticed that using GS applications (compiled from source, not debian
>> packages) I am unab
On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
> Hi,
>
> any of you still running G3 or anyway a non-altivec computer?
>
> I noticed that using GS applications (compiled from source, not debian
> packages) I am unable to open JPEG files, I get an Illegal instruction.
>
> (gdb)
Hi,
any of you still running G3 or anyway a non-altivec computer?
I noticed that using GS applications (compiled from source, not debian
packages) I am unable to open JPEG files, I get an Illegal instruction.
(gdb) bt
#0 0x0d243b68 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62
#1 0
18 matches
Mail list logo
