Bug#332897: marked as done (set COPTFLAGS in config files to improve performance on subarches)
Your message dated Sun, 09 Oct 2005 10:47:09 -0700
with message-id <E1EOfGP-0006rz-00@spohr.debian.org>
and subject line Bug#332897: fixed in kfreebsd-5 5.4-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Oct 2005 10:25:50 +0000
>From rmh@aybabtu.com Sun Oct 09 03:25:50 2005
Return-path: <rmh@aybabtu.com>
Received: from 216.red-62-57-140.user.auna.net (khazad.dyndns.org) [62.57.140.216]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EOYNK-0008Hn-00; Sun, 09 Oct 2005 03:25:50 -0700
Received: from rmh by khazad.dyndns.org with local (Exim 4.52)
id 1EOYNO-00016I-Tm; Sun, 09 Oct 2005 12:25:54 +0200
Content-Type: multipart/mixed; boundary="===============1524133316=="
MIME-Version: 1.0
From: Robert Millan <rmh@aybabtu.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: set COPTFLAGS in config files to improve performance on subarches
X-Mailer: reportbug 3.17
Date: Sun, 09 Oct 2005 12:25:54 +0200
Message-Id: <[🔎] E1EOYNO-00016I-Tm@khazad.dyndns.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
This is a multi-part MIME message sent by reportbug.
--===============1524133316==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: kfreebsd-5
Severity: wishlist
Tags: patch
I'm attaching a patch that should improve performance on high subarches:
- i486 gets -march=i486 and -mtune=i686
- i586 gets -march=i586
- i686 gets -march=i686
Unless this causes runtime errors, I think there's no drawback in adding -march
for the respective subarches.
For -mtune, though, it is not clear what is better. My opinion is that, since
the default kernel is the i486 one, it'll most often be used on i686, so it's
probably better to tune for that cpu (but keeping compatibility with i486).
This isn't only the case for installs on which the user didn't bother to switch
to -586 or -686, but also for Live systems that are forced to use -486.
As for i586, since they installed this package explicitly, it most likely means
we're really on a i586 cpu, so -mtune would do more harm than good.
This patch is a followup to the one in #332836.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
--===============1524133316==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="subarch-tuning.diff"
diff -ur config.old/486 config/486
--- config.old/486 2005-10-09 11:58:29.000000000 +0200
+++ config/486 2005-10-09 12:01:03.000000000 +0200
@@ -5,6 +5,7 @@
cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
+makeoptions COPTFLAGS="-march=i486 -mtune=i686"
ident Debian-i486
# To statically compile in device wiring instead of /boot/device.hints
diff -ur config.old/586 config/586
--- config.old/586 2005-10-09 11:58:29.000000000 +0200
+++ config/586 2005-10-09 12:01:15.000000000 +0200
@@ -4,6 +4,7 @@
machine i386
cpu I586_CPU
cpu I686_CPU
+makeoptions COPTFLAGS="-march=i586"
ident Debian-i586
# To statically compile in device wiring instead of /boot/device.hints
diff -ur config.old/686 config/686
--- config.old/686 2005-10-09 11:56:00.000000000 +0200
+++ config/686 2005-10-09 12:01:29.000000000 +0200
@@ -3,6 +3,7 @@
machine i386
cpu I686_CPU
+makeoptions COPTFLAGS="-march=i686"
ident Debian-i686
# To statically compile in device wiring instead of /boot/device.hints
diff -ur config.old/686-smp config/686-smp
--- config.old/686-smp 2005-10-09 11:56:00.000000000 +0200
+++ config/686-smp 2005-10-09 12:01:42.000000000 +0200
@@ -3,6 +3,7 @@
machine i386
cpu I686_CPU
+makeoptions COPTFLAGS="-march=i686"
ident Debian-i686-SMP
# To statically compile in device wiring instead of /boot/device.hints
--===============1524133316==--
---------------------------------------
Received: (at 332897-close) by bugs.debian.org; 9 Oct 2005 17:49:03 +0000
>From katie@spohr.debian.org Sun Oct 09 10:49:03 2005
Return-path: <katie@spohr.debian.org>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EOfGP-0006rz-00; Sun, 09 Oct 2005 10:47:09 -0700
From: Aurelien Jarno <aurel32@debian.org>
To: 332897-close@bugs.debian.org
X-Katie: $Revision: 1.56 $
Subject: Bug#332897: fixed in kfreebsd-5 5.4-2
Message-Id: <E1EOfGP-0006rz-00@spohr.debian.org>
Sender: Archive Administrator <katie@spohr.debian.org>
Date: Sun, 09 Oct 2005 10:47:09 -0700
Delivered-To: 332897-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-4.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: kfreebsd-5
Source-Version: 5.4-2
We believe that the bug you reported is fixed in the latest version of
kfreebsd-5, which is due to be installed in the Debian FTP archive:
kfreebsd-5_5.4-2.diff.gz
to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-2.diff.gz
kfreebsd-5_5.4-2.dsc
to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-2.dsc
kfreebsd-source-5.4_5.4-2_all.deb
to pool/main/k/kfreebsd-5/kfreebsd-source-5.4_5.4-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 332897@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated kfreebsd-5 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 9 Oct 2005 09:43:41 +0200
Source: kfreebsd-5
Binary: kfreebsd-image-5.4-1-686 kfreebsd-headers-5-686 kfreebsd-headers-5.4-1-686 kfreebsd-headers-5.4-1-586 kfreebsd-headers-5.4-1-486 kfreebsd-headers-5-686-smp kfreebsd-image-5.4-1-686-smp kfreebsd-headers-5-586 kfreebsd-image-5.4-1-486 kfreebsd-headers-5.4-1-686-smp kfreebsd-image-5-686-smp kfreebsd-image-5-486 kfreebsd-image-5-586 kfreebsd-headers-5-486 kfreebsd-source-5.4 kfreebsd-image-5-686 kfreebsd-headers-5.4-1 kfreebsd-image-5.4-1-586
Architecture: source all
Version: 5.4-2
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno <aurel32@debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Description:
kfreebsd-source-5.4 - source code for kernel of FreeBSD 5.4 with Debian patches
Closes: 332836 332897
Changes:
kfreebsd-5 (5.4-2) unstable; urgency=low
.
* Enabled 586 and 686 CPUs support on the 486 flavour and 686 CPUs
support on the 586 flavour (closes: bug#332836).
* Use --march to optimize flavours (closes: bug#332897).
Files:
cca905916a2adb99bb10be9e045b5cfc 1330 devel optional kfreebsd-5_5.4-2.dsc
0d9f5992e7cfb9d5f41f631929b87ef5 34213 devel optional kfreebsd-5_5.4-2.diff.gz
57ea795e67b9f6d77bee1df5f3e92274 13154772 devel optional kfreebsd-source-5.4_5.4-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDSVPyw3ao2vG823MRAjJXAKCMf53mVIGx2+b+GTEW6V2Ir1xpYQCfTTMr
bCDg+o9S0zQcwP8qN1FuyTw=
=Fnmb
-----END PGP SIGNATURE-----
Reply to: