any value in centralizing common 32/64 x86 content in vmlinux.lds.S?

  given the amount of common content between
arch/x86/kernel/vmlinux_32.lds.S and arch/x86/kernel/vmlinux_64.lds.S,
what about just defining macros for some of that stuff in
arch/x86/kernel/vmlinux.lds.S and cutting down on all the duplication?

  as is done in include/asm-generic/vmlinux.lds.S, why not just
define some handy macros, like:

#define INITRAMFS(align)					\
	. = ALIGN(align);					\
	.init.ramfs : AT(ADDR(.init.ramfs) - LOAD_OFFSET) {	\
	__initramfs_start = .;					\
	*(.init.ramfs)						\
	__initramfs_end = .;					\
	}

or something similar.

  i'm guessing there's a fair amount of content like that that can be
coalesced, no?  it would also standardize some of the niggling
differences between some of that content between the two files.

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: [PATCH] keyspan: init termios properly
• Next by Date: [PATCH] Add EXPORT_SYMBOL(ksize);
• Previous by thread: [PATCH] Remove superfluous checks for CONFIG_BLK_DEV_INITRD from initramfs.c.
• Next by thread: [PATCH] Add EXPORT_SYMBOL(ksize);
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]