Any use of a host library should come with associated configure options to
specify header and library paths for that library (and documentation for
those options). (See existing --with-gmp*, --with-isl* etc. options.)
--
Joseph S. Myers
jos...@codesourcery.com
Hi Martin,
LTO bytecode is not supposed to be a distributable format.
One of my dreams is to make libgfortran LTO-clean. There is
a lot of performance to be gained both in I/O (where a huge
number of special cases could be shortcut by LTO, because
hardly any program uses them all) and in arra
> On 6/20/19 12:58 PM, Thomas Koenig wrote:
> > Am 20.06.19 um 11:07 schrieb Martin Liška:
> >> On the contrary, decompression
> >> of zstd with zlib will end with:
> >> lto1: internal compiler error: compressed stream: data error
> >
> > Sogenerating object files on one system and trying to read
On 6/20/19 12:58 PM, Thomas Koenig wrote:
> Am 20.06.19 um 11:07 schrieb Martin Liška:
>> On the contrary, decompression
>> of zstd with zlib will end with:
>> lto1: internal compiler error: compressed stream: data error
>
> Sogenerating object files on one system and trying to read them
> on anot
Am 20.06.19 um 11:07 schrieb Martin Liška:
On the contrary, decompression
of zstd with zlib will end with:
lto1: internal compiler error: compressed stream: data error
Sogenerating object files on one system and trying to read them
on another system which does not happen to have a particular
li
Hello.
As mentioned by Honza, it's using cmake and to be honest I prefer to use a
shared
library than a statically build library. Moreover, it's an optional requirement
and
so that we don't have to include that to contrib/download_prerequisites.
I like the idea of marking of compression algorit
