public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38574]  New: -fvisibility=hidden not affecting thread variables while attribute hidden does.
Date: Thu, 18 Dec 2008 22:21:00 -0000	[thread overview]
Message-ID: <bug-38574-507@http.gcc.gnu.org/bugzilla/> (raw)

Compile the following, with "-O2 -fvisibility=hidden -S" without/with -DH. 
Compare assembly code. For this target, you'll see the following diff, but the
difference was noticed on the CRIS TLS w.i.p. using [gcc-4_3-branch revision
135713]:

--- hh.s        2008-12-18 23:14:54.000000000 +0100
+++ h.s 2008-12-18 23:15:05.000000000 +0100
@@ -13,5 +13,6 @@ foo:
        popl    %ebp
        ret
        .size   foo, .-foo
+       .hidden xyzzy
        .ident  "GCC: (GNU) 4.3.0 20080428 (Red Hat 4.3.0-8)"
        .section        .note.GNU-stack,"",@progbits


-- 
           Summary: -fvisibility=hidden not affecting thread variables while
                    attribute hidden does.
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2008-12-18 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 22:21 hp at gcc dot gnu dot org [this message]
2008-12-18 22:22 ` [Bug middle-end/38574] " hp at gcc dot gnu dot org
2008-12-18 22:31 ` pinskia at gcc dot gnu dot org
2008-12-18 22:31 ` [Bug target/38574] " pinskia at gcc dot gnu dot org
2008-12-18 22:37 ` [Bug middle-end/38574] " hp at gcc dot gnu dot 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-38574-507@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).