public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/49500] New: [4.7 Regression]: gcc.dg/tls/alias-1.c
Date: Wed, 22 Jun 2011 03:57:00 -0000	[thread overview]
Message-ID: <bug-49500-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.7 Regression]: gcc.dg/tls/alias-1.c
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: hubicka@gcc.gnu.org


With revision 175164 this test passed.
>From revision 175170 and on, this test has failed as follows:

Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/tls/tls.exp ...
FAIL: gcc.dg/tls/alias-1.c (test for excess errors)

The message in gcc.log being:
Executing on host: /tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/xgcc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/tls/alias-1.c    -ansi
-pedantic-errors   -isystem
/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc1/gcc/newlib/libc/include
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris/
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris
-L/tmp/hpautotest-gcc1/gcc/libgloss/cris 
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib -sim3  -lm   -o
alias-1.exe    (timeout = 300)
/tmp/ccjevxvZ.o: In function `_main':
alias-1.c:(.text+0xc): undefined reference to `___emutls_v.bar'
collect2: error: ld returned 1 exit status
compiler exited with status 1
output is:
/tmp/ccjevxvZ.o: In function `_main':
alias-1.c:(.text+0xc): undefined reference to `___emutls_v.bar'
collect2: error: ld returned 1 exit status

FAIL: gcc.dg/tls/alias-1.c (test for excess errors)
Excess errors:
alias-1.c:(.text+0xc): undefined reference to `___emutls_v.bar'

FWIW, cris-elf is an emutls target and I see on gcc-testresults@ that this test
fails for other emutls target since about that revision range.

Author of patches in suspect revision range CC:ed.


             reply	other threads:[~2011-06-22  3:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22  3:57 hp at gcc dot gnu.org [this message]
2011-06-22  9:15 ` [Bug regression/49500] " rguenth at gcc dot gnu.org
2011-06-22 10:09 ` ramana at gcc dot gnu.org
2011-06-22 14:05 ` danglin at gcc dot gnu.org
2011-06-23 17:12 ` hubicka at gcc dot gnu.org
2011-06-23 19:44 ` hubicka at gcc dot gnu.org
2011-06-23 21:36 ` dave at hiauly1 dot hia.nrc.ca
2011-07-01 10:48 ` hubicka at gcc dot gnu.org
2011-07-01 15:33 ` dave.anglin at bell dot net
2011-07-04 17:28 ` dave.anglin at bell dot net
2011-07-11 22:07 ` hp at gcc dot gnu.org
2011-07-12 16:35 ` uweigand at gcc dot gnu.org
2011-08-02 14:31 ` [Bug middle-end/49500] " rguenth at gcc dot gnu.org
2011-08-02 14:35 ` amylaar at gcc dot gnu.org
2011-08-02 15:44 ` hp at gcc dot gnu.org
2011-08-03 20:12 ` hubicka at gcc dot gnu.org
2011-08-05 20:53 ` hubicka at gcc dot gnu.org
2011-08-09  0:17 ` hp 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-49500-4@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).