From: Leo Famulari <leo@famulari.name>
To: 24290@debbugs.gnu.org
Subject: bug#24290: ImageMagick optimized for the host processor type on x86_64 and i686
Date: Mon, 22 Aug 2016 22:00:20 -0400 [thread overview]
Message-ID: <20160823020020.GA961@jasmine> (raw)
When building ImageMagick on i686 and x86_64, the '-mtune' GCC option
[0] is automatically set to optimize the output for the host processor
[1].
My understand of the GCC documentation is that the binaries will still
run on other processor types, which is why we haven't noticed any
related problems with ImageMagick so far.
But, this definitely makes the ImageMagick package non-reproducible.
Potential solutions:
* Set '-mtune=generic' when building on x86_64 and i686.
* Patch the build system to not try setting this flag at all. I'm not
sure how to achieve this, but I'm sure it's possible.
* Your great idea here :)
These are the two files that contain the string '-mtune' in the
ImageMagick source tree:
http://git.imagemagick.org/repos/ImageMagick/blob/ImageMagick-6/m4/ax_gcc_archflag.m4
I recommend *not* opening this file in your browser. It's very long and
might crash your browser. Try cloning the Git repo instead.
hXXp://git.imagemagick.org/repos/ImageMagick/blob/ImageMagick-6/configure
[0]
https://gcc.gnu.org/onlinedocs/gcc-4.9.4/gcc/i386-and-x86-64-Options.html#i386-and-x86-64-Options
[1]
http://hydra.gnu.org/build/1441619/log#line-2626
[...]
checking whether C compiler accepts -mtune=haswell... yes
checking for gcc architecture flag... -mtune=haswell
[...]
next reply other threads:[~2016-08-23 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 2:00 Leo Famulari [this message]
2016-08-23 2:40 ` bug#24290: [PATCH 0/1] Potential solution Leo Famulari
2016-08-23 2:40 ` bug#24290: [PATCH 1/1] gnu: imagemagick: Don't build with processor-specific optimizations Leo Famulari
2016-08-23 4:53 ` Eric Bavier
2016-08-23 16:45 ` Leo Famulari
2016-08-24 20:00 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160823020020.GA961@jasmine \
--to=leo@famulari.name \
--cc=24290@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).