mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@home-tj.org>
To: linux-kernel@vger.kernel.org
Cc: kai@germaschewski.name
Subject: [PATCH] patsubstfor LOCALVERSION and -fno-omit-frame-pointer
Date: Sun, 12 Sep 2004 18:36:35 +0900	[thread overview]
Message-ID: <20040912093635.GD13359@home-tj.org> (raw)

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

 (** Sorry, I'm resending this mail.  I had written the subject in the
Reply-To field. **)

 Hello, I'm attaching two patches for the top Makefile.

 The first patch modifies LOCALVERSION definition such taht it uses
patsubst instead of subst to remove surrounding double quotes from
CONFIG_LOCALVERSION.  This helps syntax-highlighting editors.

 The second patch addes -fno-omit-frame-pointer to CFLAGS when
CONFIG_FRAME_POINTER is set.  My gcc (gcc-3.3.4 Debian 1:3.3.4-11)
automatically turns on -fomit-frame-pointer when -O2 is specified and
thus breaks CONFIG_FRAME_POINTER option.  I'm not sure if other
versions of gcc wouldn't choke with -fno-omit-frame-pointer.  My 2.95
(2.95.4) seems to be OK though.

-- 
tejun


[-- Attachment #2: patsubst_localversion.patch --]
[-- Type: text/plain, Size: 884 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/09/12 16:29:12+09:00 tj@htj.dyndns.org 
#   Use patsubst instead of subst to remove surrounding double quotes
#   from CONFIG_LOCALVERSION.  This helps syntax-highlighting editors.
# 
# Makefile
#   2004/09/12 16:29:06+09:00 tj@htj.dyndns.org +1 -1
#   Use patsubst instead of subst to remove surrounding double quotes
#   from CONFIG_LOCALVERSION.  This helps syntax-highlighting editors.
# 
diff -Nru a/Makefile b/Makefile
--- a/Makefile	2004-09-12 18:04:33 +09:00
+++ b/Makefile	2004-09-12 18:04:33 +09:00
@@ -157,7 +157,7 @@
 
 LOCALVERSION = $(subst $(space),, \
 	       $(shell cat /dev/null $(localversion-files)) \
-	       $(subst ",,$(CONFIG_LOCALVERSION)))
+	       $(patsubst "%",%,$(CONFIG_LOCALVERSION)))
 
 KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)$(LOCALVERSION)
 

[-- Attachment #3: noomitframepointer.patch --]
[-- Type: text/plain, Size: 883 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/09/12 16:31:46+09:00 tj@htj.dyndns.org 
#   Newer gcc versions automatically turns on -fomit-frame-pointer when
#   -O2 is specified thus breaking CONFIG_FRAME_POINTER option.
#   Explicitly specifying -fno-omit-frame-pointer fixes it.
# 
# Makefile
#   2004/09/12 16:31:40+09:00 tj@htj.dyndns.org +3 -1
#   Newer gcc versions automatically turns on -fomit-frame-pointer when
#   -O2 is specified thus breaking CONFIG_FRAME_POINTER option.
#   Explicitly specifying -fno-omit-frame-pointer fixes it.
# 
diff -Nru a/Makefile b/Makefile
--- a/Makefile	2004-09-12 18:04:54 +09:00
+++ b/Makefile	2004-09-12 18:04:54 +09:00
@@ -486,7 +486,9 @@
 CFLAGS		+= -O2
 endif
 
-ifndef CONFIG_FRAME_POINTER
+ifdef CONFIG_FRAME_POINTER
+CFLAGS		+= -fno-omit-frame-pointer
+else
 CFLAGS		+= -fomit-frame-pointer
 endif
 

             reply	other threads:[~2004-09-12  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-12  9:36 Tejun Heo [this message]
2004-10-17  0:01 ` Sam Ravnborg

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=20040912093635.GD13359@home-tj.org \
    --to=tj@home-tj.org \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®