This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mliska@suse.cz
Recipients mliska@suse.cz
Date 2015-07-01.10:41:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435747274.99.0.734466851501.issue24543@psf.upfronthosting.co.za>
In-reply-to
Content
I've just tried to build Python with {C,CXX,LD}FLAGS set to '-flto'.

Unfortunately following conftest source file is fragile:

cat /tmp/mc.c
int
main ()
{

  unsigned int fpcr;
  __asm__ __volatile__ ("fmove.l %%fpcr,%0" : "=g" (fpcr));
  __asm__ __volatile__ ("fmove.l %0,%%fpcr" : : "g" (fpcr));

  ;
  return 0;
}

gcc --version:
gcc (GCC) 5.1.1 20150424 (prerelease)

gcc -c /tmp/mc.c
/tmp/mc.c: Assembler messages:
/tmp/mc.c:6: Error: no such instruction: `fmove.l %fpcr,%eax'
/tmp/mc.c:7: Error: no such instruction: `fmove.l -4(%rbp),%fpcr'

gcc -flto -c /tmp/mc.c

As GCC does not produce assembly with -flto and -c (unless you append -ffat-lto-objects), the compilation success.

Can you please write more robust configuration.
Thanks,
Martin
History
Date User Action Args
2015-07-01 10:41:15mliska@suse.czsetrecipients: + mliska@suse.cz
2015-07-01 10:41:14mliska@suse.czsetmessageid: <1435747274.99.0.734466851501.issue24543@psf.upfronthosting.co.za>
2015-07-01 10:41:14mliska@suse.czlinkissue24543 messages
2015-07-01 10:41:14mliska@suse.czcreate