[Bug libitm/64360] New: libitm.c/stackundo.c fails with -fpic

[Bug libitm/64360] New: libitm.c/stackundo.c fails with -fpic

[hjl.tools at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64360

            Bug ID: 64360
           Summary: libitm.c/stackundo.c fails with -fpic
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libitm
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com

/build/gnu/gcc/build-x86_64-linux/gcc/
/export/gnu/import/git/gcc/libitm/testsuite/libitm.c/stackundo.c
-B/export/build/gnu/gcc/build-x86_64-linux/x86_64-unknown-linux-gnu/./libitm/
-I/export/build/gnu/gcc/build-x86_64-linux/x86_64-unknown-linux-gnu/./libitm
-I/export/gnu/import/git/gcc/libitm/testsuite/.. -fmessage-length=0 -fgnu-tm
-O2
-L/export/build/gnu/gcc/build-x86_64-linux/x86_64-unknown-linux-gnu/./libitm/.libs
-lm -fpic -o ./stackundo.exe
/export/gnu/import/git/gcc/libitm/testsuite/libitm.c/stackundo.c:19:9: error:
unsafe function call 'test1' within atomic transaction
/export/gnu/import/git/gcc/libitm/testsuite/libitm.c/stackundo.c:19:9: error:
unsafe function call 'test1' within atomic transaction
FAIL: libitm.c/stackundo.c (test for excess errors)
/export/gnu/import/git/gcc/libitm/testsuite/libitm.c/stackundo.c:19:9: error:
unsafe function call 'test1' within atomic transaction
UNRESOLVED: libitm.c/stackundo.c compilation failed to produce executable

Should test1 and test2 be static?

[Bug libitm/64360] libitm.c/stackundo.c fails with -fpic

[ubizjak at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64360

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-01-15
     Ever confirmed|0                           |1

--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Confirmed.
>From gcc-bugs-return-473314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 15 10:00:32 2015
Return-Path: <gcc-bugs-return-473314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25083 invoked by alias); 15 Jan 2015 10:00:32 -0000
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
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24493 invoked by uid 48); 15 Jan 2015 10:00:22 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61523] [5 regression] Commit 211600 appears to have caused section type conflicts for ARM
Date: Thu, 15 Jan 2015 10:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-61523-4-pcHQEEMZZR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61523-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61523-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg01308.txt.bz2
Content-length: 458

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida523

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Looks like this got fixed.

[Bug libitm/64360] libitm.c/stackundo.c fails with -fpic

[hjl at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64360

--- Comment #2 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Thu Jan 15 18:03:20 2015
New Revision: 219673

URL: https://gcc.gnu.org/viewcvs?rev=219673&root=gcc&view=rev
Log:
Make test2/test1 static in libitm.c/stackundo.c

libitm.c/stackundo.c fails with -fpic since test1 and test2 may be
preempted with -fpic.  This patch makes those 2 functions static.

    PR libitm/64360
    * libitm.c/stackundo.c (test2): Make it static.
    (test1): Likewise.

Modified:
    trunk/libitm/ChangeLog
    trunk/libitm/testsuite/libitm.c/stackundo.c

[Bug libitm/64360] libitm.c/stackundo.c fails with -fpic

[hjl.tools at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64360

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |5.0

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed.