[Bug gas/22553] .largecomm, .lbss, .ldata, and .lrodata are still not documented after many, many years

[john at buu dot ac.th]

https://sourceware.org/bugzilla/show_bug.cgi?id=22553

--- Comment #9 from john at buu dot ac.th ---
Are you telling me with a streight face to go to your proprietary competitor's
documentation for an antique and dead operating system to learn about Linux
when you are working for the acknowledged premier commercial support
organization for Linux?  Uh-huh, I guess it's some strange humor that I cannot
understand due to cultural differences.

Anyway, I want to say thanks for changing what you could.  I did my part by
reporting the bug.  You did what you could fixing what you could.

But please don't be like the Hitchhiker's guide to the galaxy:

https://www.goodreads.com/quotes/40705-but-the-plans-were-on-display-on-display-i-eventually

________________________________________
From: nickc at redhat dot com address@hidden
Sent: Friday, January 12, 2018 5:36 PM
To: John Gatewood Ham
Subject: [Bug gas/22553] .largecomm, .lbss, .ldata, and .lrodata are still not
documented after many, many years

https://sourceware.org/bugzilla/show_bug.cgi?id=22553

--- Comment #8 from Nick Clifton <nickc at redhat dot com> ---
Hi John,

> I suspect the section name thing uses unwritten or perhaps Red Hat in-house
> non-public rules,

Hang on - I must stop you there.  These section names are nothing to do with
Red Hat.  (Despite my email address, I wear two hats, and at the moment I am
wearing my FSF hat).  Plus these names *are* public.  You will find the .lbss,
.ldata and .lrodata section s documented in the Solaris linker manual for
example:

  https://docs.oracle.com/cd/E26502_01/html/E26507/chapter7-1.html

Or in this book from google:


https://books.google.co.uk/books?id=qjUqDwAAQBAJ&pg=PA318&lpg=PA318&dq=.lbss+section&source=bl&ots=f-kUHrwRjy&sig=V7Ms2dQ_YsBygp86DjHSNvWGYQQ&hl=en&sa=X&ved=0ahUKEwi7pYDEnNLYAhWFBcAKHZwHDgYQ6AEIQDAF#v=onepage&q=.lbss%20section&f=false

Cheers
  Nick

--
You are receiving this mail because:
You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.