public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/52545] output.h: SECTION_EXCLUDE flag clobbers SECTION_MACH_DEP
Date: Fri, 09 Mar 2012 20:28:00 -0000	[thread overview]
Message-ID: <bug-52545-4-bciGqgGupA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52545-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52545

--- Comment #4 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-03-09 20:27:42 UTC ---
(In reply to comment #3)
> Right, I was not looking at SECTION_MACH_DEP when I defined the macro. Is it ok
> to just bump SECTION_MACH_DEP?
> 
> The patch I have in mind is:
> 
> -#define SECTION_MACH_DEP 0x2000000 /* subsequent bits reserved for target */
> -#define SECTION_EXCLUDE  0x4000000
> +#define SECTION_EXCLUDE 0x2000000
> +#define SECTION_MACH_DEP 0x8000000 /* subsequent bits reserved for target */
> 
> I can bump SECTION_MACH_DEP even more to reserve more bits.

The reserved bits start at SECTION_MACH_DEP, with the patch above you just
waste the bit at 0x4000000.

Any bits covered by 
  SECTION_MACH_DEP * (~0)
are reserved for the machine. The bigger SECTION_MACH_DEP is, the less bits are
left for machine specific needs.

Machine specific section flag masks could be, e.g.:

#define SECTION_FLAG_MACH_1 (SECTION_MACH_DEP)
#define SECTION_FLAG_MACH_2 (SECTION_MACH_DEP << 1)
#define SECTION_FLAG_MACH_3 (SECTION_MACH_DEP << 2)
...


  parent reply	other threads:[~2012-03-09 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 19:14 [Bug other/52545] New: " gjl at gcc dot gnu.org
2012-03-09 19:18 ` [Bug other/52545] " gjl at gcc dot gnu.org
2012-03-09 19:22 ` gjl at gcc dot gnu.org
2012-03-09 19:37 ` tmsriram at google dot com
2012-03-09 20:28 ` gjl at gcc dot gnu.org [this message]
2012-03-09 21:31 ` tmsriram at google dot com
2012-03-12 18:23 ` gjl at gcc dot gnu.org
2012-03-22 10:49 ` gjl at gcc dot gnu.org
2012-03-22 10:49 ` gjl at gcc dot gnu.org

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=bug-52545-4-bciGqgGupA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).