All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: [RFC] Add __initbss section
Date: Sun, 04 Nov 2007 09:29:05 +0100	[thread overview]
Message-ID: <472D82D1.1050401@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710191239490.13279@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
> On Thu, 18 Oct 2007, Franck Bui-Huu wrote:
>> After spending some fun time trying several different configurations
>> with gcc and ld, I noticed that gcc makes a section with @nobits
>> attribute if the section name starts with .bss.*
> 
>  Exactly how GCC sets section flags is mostly determined by 
> default_section_type_flags() in gcc/varasm.c; some flags are set elsewhere 
> too.  This is with HEAD of GCC.
> 

It seems that we can rely on this behaviour. I looked at gcc 4.1.2/3.2
sources and they made a section part of .bss if the section name starts
with ".bss.".

>> Another test I did is to put .init.bss (not .bss.init) section right
>> before .bss section in order to have only one segment to load. And it
>> makes magically ld do the right thing. I must admit that I don't
>> understand why, and the lack of documentation doesn't help...
> 
>  Hmm, isn't what `info ld' says enough?

Hmm, I'm must be blind but I missed that each time I read it. Could
you point out the section number please ?

OK, I think the best thing to do now is to respin the patchset and
submit it linux arch mailing list.

thanks,

		Franck

  reply	other threads:[~2007-11-04  8:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  9:52 [RFC] Add __initbss section Franck Bui-Huu
2007-10-11  9:54 ` [PATCH 1/2] Add .init.bss section Franck Bui-Huu
2007-10-11  9:58 ` [PATCH 2/2] Add .init.bss section for MIPS Franck Bui-Huu
2007-10-11 12:44 ` [RFC] Add __initbss section Ralf Baechle
2007-10-11 13:35   ` Maciej W. Rozycki
2007-10-11 14:00     ` Ralf Baechle
2007-10-11 14:49       ` Maciej W. Rozycki
2007-10-14 19:42   ` Franck Bui-Huu
2007-10-15 16:01     ` Ralf Baechle
2007-10-16  8:33       ` Franck Bui-Huu
2007-10-11 13:19 ` Maciej W. Rozycki
2007-10-14 19:52   ` Franck Bui-Huu
2007-10-15 12:19     ` Maciej W. Rozycki
2007-10-15 20:06       ` Franck Bui-Huu
2007-10-16 10:29         ` Maciej W. Rozycki
2007-10-18 20:28           ` Franck Bui-Huu
2007-10-19 11:59             ` Maciej W. Rozycki
2007-11-04  8:29               ` Franck Bui-Huu [this message]
2007-11-05 12:38                 ` Maciej W. Rozycki
2007-11-05 20:32                   ` Franck Bui-Huu
2007-10-11 15:26 ` Thiemo Seufer
2007-10-11 16:16   ` Maciej W. Rozycki
2007-10-11 16:25     ` Ralf Baechle
2007-10-11 17:07       ` Maciej W. Rozycki
2007-10-11 16:39     ` Thiemo Seufer
2007-10-14 19:53   ` Franck Bui-Huu

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=472D82D1.1050401@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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.