All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: sam@ravnborg.org, kai@tp1.ruhr-uni-bochum.de, greg@kroah.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc for 2.5.59 bk
Date: Tue, 18 Feb 2003 04:17:16 -0500	[thread overview]
Message-ID: <3E51FA1C.7060807@pobox.com> (raw)
In-Reply-To: <1144.62.20.229.212.1045558700.squirrel@www.zytor.com>

[-- Attachment #1: Type: text/plain, Size: 355 bytes --]

H. Peter Anvin wrote:
> However, I can personally vouch for that it's *not* fixed for the main
> kernel build as of 2.5.61.


Well, if I had a Transmeta-powered laptop or handheld, I'm sure that 
would be fixed too ;-)

Can you give the attached patch a quick once-over?  It's obvious enough 
but I would rather the patch got tested nonetheless.

	Jeff



[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1465 bytes --]

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1051  -> 1.1052 
#	  arch/i386/Makefile	1.44    -> 1.45   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/02/18	jgarzik@redhat.com	1.1052
# [ia32] fix Crusoe CFLAGS on newer gcc versions
# --------------------------------------------
#
diff -Nru a/arch/i386/Makefile b/arch/i386/Makefile
--- a/arch/i386/Makefile	Tue Feb 18 04:15:39 2003
+++ b/arch/i386/Makefile	Tue Feb 18 04:15:39 2003
@@ -39,7 +39,8 @@
 cflags-$(CONFIG_MK6)		+= $(call check_gcc,-march=k6,-march=i586)
 cflags-$(CONFIG_MK7)		+= $(call check_gcc,-march=athlon,-march=i686 -malign-functions=4)
 cflags-$(CONFIG_MK8)		+= $(call check_gcc,-march=k8,$(call check_gcc,-march=athlon,-march=i686 -malign-functions=4))
-cflags-$(CONFIG_MCRUSOE)	+= -march=i686 -malign-functions=0 -malign-jumps=0 -malign-loops=0
+cflags-$(CONFIG_MCRUSOE)	+= -march=i686
+cflags-$(CONFIG_MCRUSOE)	+= $(call check_gcc,-falign-functions=0 -falign-jumps=0 -falign-loops=0,-malign-functions=0 -malign-jumps=0 -malign-loops=0)
 cflags-$(CONFIG_MWINCHIPC6)	+= $(call check_gcc,-march=winchip-c6,-march=i586)
 cflags-$(CONFIG_MWINCHIP2)	+= $(call check_gcc,-march=winchip2,-march=i586)
 cflags-$(CONFIG_MWINCHIP3D)	+= -march=i586

  reply	other threads:[~2003-02-18  9:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  4:59 [RFC] klibc for 2.5.59 bk Greg KH
2003-02-07  5:06 ` H. Peter Anvin
2003-02-07  5:10   ` Greg KH
2003-02-07 15:00 ` Alex Riesen
2003-02-09 12:57   ` Greg KH
2003-02-17  3:06     ` Kai Germaschewski
2003-02-17  5:50       ` Jeff Garzik
2003-02-17 18:02       ` Sam Ravnborg
2003-02-17 18:07         ` H. Peter Anvin
2003-02-17 18:36           ` Jeff Garzik
2003-02-17 18:57             ` Sam Ravnborg
2003-02-17 19:24               ` Jeff Garzik
2003-02-18  8:58             ` H. Peter Anvin
2003-02-18  9:17               ` Jeff Garzik [this message]
2003-02-18  9:36                 ` Stelian Pop
2003-02-18  9:37                   ` Stelian Pop
2003-02-18  9:46                     ` Jeff Garzik
2003-02-18  9:45                   ` Jeff Garzik
2003-02-18  9:56                     ` Stelian Pop
     [not found] <20030217031008$3e63@gated-at.bofh.it>
     [not found] ` <20030217031008$270a@gated-at.bofh.it>
2003-02-17 17:12   ` Arnd Bergmann

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E51FA1C.7060807@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.