From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-221770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28733 invoked by alias); 20 Jun 2007 17:48:38 -0000
Received: (qmail 28660 invoked by uid 48); 20 Jun 2007 17:48:28 -0000
Date: Wed, 20 Jun 2007 17:48:00 -0000
Subject: [Bug c/32434]  New: #pragma GCC visibility causes invalid relocation to __stach_chk_guard
X-Bugzilla-Reason: CC
Message-ID: <bug-32434-14730@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "equinox-gccbug at diac24 dot net" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2007-06/txt/msg01748.txt.bz2

When using, e.g., #pragma GCC visibility push(internal) together with
-fstack-protector and PIC code, gcc emits an invalid R_386_GOTOFF relocation to
__stack_chk_guard.

(Testcase follows)

Note that the problem does not happen with -fvisibility,
__attribute__((visibility)) or when there is a reference to __stack_chk_guard
before the #pragma.


-- 
           Summary: #pragma GCC visibility causes invalid relocation to
                    __stach_chk_guard
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: equinox-gccbug at diac24 dot net
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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