On Sun, May 24, 2020 at 10:14:49PM +0200, Stefan Weil wrote:
> Adrian, I am afraid that there is a misunderstanding.
>
> The code part which is compiled with -march=native is never executed by
> default.
I get that point.
> There is a command line option which allows users to select the code
>
Adrian, I am afraid that there is a misunderstanding.
The code part which is compiled with -march=native is never executed by
default.
There is a command line option which allows users to select the code
which is used for certain time critical calculations (dot product). A
wrong choice is not a
Control: severity -1 serious
On Fri, Jan 24, 2020 at 10:28:36PM +0100, Stefan Weil wrote:
> Am 24.01.20 um 21:53 schrieb peter green:
>
> > I still don't think -march=native is appropriate for a binary
> > distribution though. If you want to offer different versions of the
> > code built with
> For example, default compiler flags in Debian unstable now:
> $ dpkg-buildflags --get CXXFLAGS
> -g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat
> -Werror=format-security
> $ dpkg-buildflags --get CFLAGS
> -g -O2 -fdebug-prefix-map=/home/boris=.
Hi,
> I see the problem of builds which depend on an autobuilder which may be
> different for each build. What would be the best solution for
> distributions?
1) Special configuration option, which disables all CPU specific optimizations
in compiler flags.
or
2) Special configuration
Am 24.01.20 um 21:53 schrieb peter green:
> I still don't think -march=native is appropriate for a binary
> distribution though. If you want to offer different versions of the
> code built with different CPU requirements, that is fine, but please
> don't let them depend on what CPU happens to be
Severity 949638 normal
Thanks
On 24/01/2020 19:16, Stefan Weil wrote:
As far as I know all Linux distributions use the autoconf based build,
Debian certainly does appear to be using the autoconf based build.
The default autoconf build uses -march=native only if it is supported by
the compiler
It is not necessary to patch Tesseract code if for whatever reason
-march=native is completely unwanted.
`make libtesseract_native_la_CXXFLAGS=` will override the extra compiler
flags which are used to produce the native code, so only the default
flags which don't include -march=native will be
> The URL for the patch is 404.
s/tessarect/tesseract/
The fixed URL is https://debdiffs.raspbian.org/main/t/tesseract/.
Stefan
Am 24.01.20 um 19:55 schrieb Jeff Breidenbach:
>
> Regarding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638
>
> Thank you, Peter.
>
> 1. The URL for the patch is 404.
>
> 2. There may be some subtlety with -march=native, specifically related to
> detection of SIMD instructions like
BCC: Stefan Weil since I don't know if he wants his email posted in
bugs.debian.org
Regarding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638
Thank you, Peter.
1. The URL for the patch is 404.
2. There may be some subtlety with -march=native, specifically related to
detection of
Package: tesseract
Version: 4.1.0-1
Severity: serious
Tags: patch
I recently discovered that tesseract 4.1.1-1 failed the armv7 contamination
check we run in raspbian.
Investigating shows that since version 4.1.0-1 tesseract started using
-march=native. This compiler option is totally
12 matches
Mail list logo
