All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix setting of sn_hub_info->shub_1_1_found
Date: Mon, 06 Jun 2005 17:04:21 +0000	[thread overview]
Message-ID: <jepsuz8lii.fsf@sykes.suse.de> (raw)
In-Reply-To: <42A04C38.mailxA351PB0RI@aqua.americas.sgi.com>

David Mosberger <davidm@napali.hpl.hp.com> writes:

>>>>>> On Sat, 04 Jun 2005 14:18:16 +1000, Keith Owens <kaos@sgi.com> said:
>
>   Keith> On Fri, 3 Jun 2005 11:50:55 -0700, 
>   Keith> "Luck, Tony" <tony.luck@intel.com> wrote:
>   >>> This explains why XPC has been so troublesome to load on older systems.
>   >>> Thanks Dean!
>   >>> 
>   >>> Tony, can this still get into 2.6.12?
>   >> 
>   >> Probably ... but the first hunk of the patch looks like a no-op,
>   >> and contravenes some style guidlines about initializing global
>   >> variables to 0.
>   >> 
>   >> -static int shub_1_1_found __initdata;
>   >> +static int __initdata shub_1_1_found = 0;
>
>   Keith> There is a linker restriction that you must initialise variables that
>   Keith> are to be stored in different sections, which is what __initdata does.
>   Keith> without initialization shub_1_1_found ends up in .bss, with
>   Keith> initialization it ends up in .init.data.
>
> Interesting.  Strikes me as a toolchain-bug, though.  Clearly the
> __initdata declaration is in conflict with putting the data in .bss,
> yet there is no warning or error.

Can't reproduce that with gcc 3.2, or anything newer.

$ cat section.c
int __attribute__((section(".init.data"))) foo;
$ gcc -S section.c
$ cat section.s
	.file	"section.c"
	.pred.safe_across_calls p1-p5,p16-p63
	.global foo#
	.section	.init.data,"aw",@progbits
	.align 4
	.type	foo#,@object
	.size	foo#,4
foo:
	.skip	4
	.ident	"GCC: (GNU) 3.2.2"

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2005-06-06 17:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 12:25 [PATCH] fix setting of sn_hub_info->shub_1_1_found Dean Nelson
2005-06-03 13:58 ` Robin Holt
2005-06-03 18:50 ` Luck, Tony
2005-06-03 19:14 ` Dean Nelson
2005-06-03 19:36 ` Luck, Tony
2005-06-03 19:43 ` Dean Nelson
2005-06-03 19:57 ` Luck, Tony
2005-06-03 21:09 ` Russ Anderson
2005-06-03 21:21 ` David Mosberger
2005-06-04  4:18 ` Keith Owens
2005-06-06  5:05 ` Luck, Tony
2005-06-06 16:57 ` David Mosberger
2005-06-06 17:04 ` Andreas Schwab [this message]
2005-06-06 17:25 ` David Mosberger

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=jepsuz8lii.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-ia64@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 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.